Element management system with tree-structured representations

ABSTRACT

A network element management system in which network elements can be grouped, and viewed and manipulated by groups. This provides both greater ease of use and faster response.

CROSS-REFERENCE TO OTHER APPLICATION

[0001] This application claims priority from U.S. Provisionalapplication 60/135,883 filed May 26 1999, which is hereby incorporatedby reference.

BACKGROUND AND SUMMARY OF THE INVENTION

[0002] The present application relates to telecommunication systems, andparticularly to element management systems which remotely managetelecommunications network elements.

Background: Telecommunications Network Structure

[0003] The advance of modern telecommunications technology, and theincreasing use of data bandwidth by many businesses, has resulted in anincreasing amount of traffic flowing to an increasing number of nodes.The data bandwidths which can be handled by fiber optic lines have madelong-distance data transmission much cheaper, but have required complexelectronics for combining substreams of data and routing each to itsproper destination. The telecommunications infrastructure includes awide variety of network elements, each of which may include a number ofcomplex programmable subsystems. With the explosive growth intechnological capabilities, many vendors have been making rapidimprovements in their network element components.

[0004] Telecommunications networks are complex to design, build, andmaintain. Ever increasing demands for improvements, greater bandwidth,ease of use, and interoperability add to this complexity and requireincreasingly capable network management. Service providers requirenetwork management systems that can accommodate equipment and componentsthat comply with a variety of interface standards.

Background: Developments in Diversity of Network Elements

[0005] It should be noted that the terms “network element” and “elementmanager” are also sometimes used in reference to computer networksrather than telecommunications networks. However, the requirements forelement management in such networks are vastly different from thoserelevant to telecommunications networks. First, telecommunicationsnetworks are normally have a far larger number of nodes. Second, datastream routing is the primary purpose of telecommunications networks,while in computing networks switching is performed merely when requiredto link resources demanded by a particular task. (Indeed a WAN willtypically be implemented using data channels provided by atelecommunications network operator, so it can be seen that thetelecommunications network, in such cases is regarded as a more“fundamental” level on which the connectivity of the WAN can be allowedto depend.) Third, the reliability requirements of telecommunicationsnetworks are extremely high, and can be much higher than those of somecomputer networks. Fourth, a telecommunications network typicallyincludes far more nodes which are physically remote. Fifth, the ratio ofprocessor operations to data bits transmitted is typically different bymany orders of magnitude.

[0006] The network elements are each a complex system which includesmany complex programmable subsystems. These programmable subsystems havelocal memories which store their programming and maintain a record oftheir operating history. The data in these many local memories isimportant for auditing system integrity and reliability.

Background: Element Management Systems (EMSs)

[0007] Element management systems are used by telecommunications systemoperators to monitor telecommunications network elements, and changesignal switching and routing as required. Conventionally a single“network element” is considered to include a number of independentlyprogrammable switching cards (typically one or more shelves full, i.e.tens of cards). Since each card is itself a complex programmable system,the total programmability of a modern network element is very large.

[0008] Element management is not a trivial task, since each networkelement includes many complex programmable subsystems, and since veryhigh reliability is required. Element management is rapidly becomingmore difficult, since the number of possible programmed states in eachnetwork element is steadily increasing.

[0009] For example, a typical card might have four bidirectional OC-3interfaces, for a total bandwidth of more than half a gigabaud in eachdirection. Each OC-3 data stream is resolved into three STS-1 datastreams, which in turn are each resolved into 28 data streams at T1 rate(approximately 1.5 million bits per second each). Thus the card canredirect 84 different channels within each of its four data connections.Even without cross-connect options, the theoretically possible number ofin/out switching states is 336 factorial (336×335×334× . . . ×3×2×1).The theoretically possible number of switching states for a networkelement which includes 30 such cards will be in the neighborhood of thisnumber raised to the 30th power, which is a very large number (of theorder of 10²¹¹³⁸).

[0010] As the demand for bandwidth increases, hierarchical switchingrelations are appearing. For example, currently proposed WDM cards wouldhandle routing of 168 OC-192 channels, each carrying about 10 gigabaud(ten billion bits per second). Each of those OC-192 data streams wouldthen be further manipulated by an OC-192 switching card, which woulddivide the OC-192 data streams down into (for example) OC-3 datastreams, for routing to an OC-3 switching card. (For comparison,ordinary voice connections require only about 56 kilobits per secondeach, which is much smaller than the smallest data channel of the OC-3card mentioned above.)

[0011] An opposite trend, which also makes element management moredifficult, is the larger size of networks. Telecommunications networksunderwent a fundamental change in their locational economics in the lastdecades of the 20th century. This change began when microwave linksreplaced copper, but in recent years has been driven by the very highbandwidths provided by fiber optic trunk lines. In this new era oflocational economics, the physical distance between signal originationand destination points became much less important than it had beenpreviously; and a corollary of this was that economies of scale drovetelecommunications networks to increasingly larger sizes (whethermeasured geographically, or by numbers of nodes, or by bandwidthswitched).

[0012] The trend to larger networks has also been driven by theincreasingly global span of telecommunications carriers. Large carriershave networks which extend over tens of thousands of miles, and theyneed reliable tools for monitoring and controlling these very large andvery far-flung networks.

[0013] The larger sizes of networks, in turn, mean that astate-of-the-art network element management system must be able to copewith thousands of network elements, each containing tens of cards whicheach are programmable to switch hundreds of channels.

[0014] A further pressure on element management systems is applied bycustomer demand for fast response: a corporate user of bandwidth whichrequests additional capacity will be severely hampered if the responseis not prompt.

[0015] The telecommunications network is never static, but iscontinually changing, in response to operator inputs as well as toequipment changes. Conventionally the operator inputs which commandchanges have been stored in a log file; but this results in a large textfile which is extremely difficult to search. While in theory such alarge text file can be searched for debugging or to ascertain thecurrent state, in practice the present inventors have found that this isdifficult.

[0016] Conventional element management systems (EMSs) have beenvendor-specific, so that a network management system must interface tomultiple different EMSs. (A model of this interface structure is shownin FIG. 1A.)

Background: Cross-Connect Management

[0017] The number of links in a complex cross-connect cannot usefully beviewed at once, so an operator interface for cross-connect managementmust provide some way to reduce the number of links seen at once. Thisis typically done by using multiple windows to view different subsets oflinks in detail. However, the increasing number of windows means theoperators have more difficulty in bringing up the appropriate displayview to see the selected link in detail.

Background: Network, Service, and Business Management: TMN

[0018] The TMN architecture is a reference model for a hierarchicaltelecommunications management approach. Its purpose is to partition thefunctional areas of management into layers. See e.g. ITU-TRecommendation M.3010; Divakara K. Udupa, TMN: TelecommunicationsManagement Network (1999); and the Internet-published tutorial articleshttp://www.webproforum.com/acrobat/fund_telecom.pdf,http://www.webproforum.com/acrobat/oss.pdf,http://www.webproforum.com/acrobat/tmn.pdf,http://www.webproforum.com/acrobat/ems.pdf; all of which are herebyincorporated by reference.

[0019] The TMN architecture identifies five functional levels oftelecommunications management: business management layer (BML), servicemanagement layer (SML), network management layer (NML), elementmanagement layer (EML), and the (increasingly intelligent) NEs in thenetwork element layer (NEL). TMN segregates (or at least distinguishes)the management responsibilities based on these layers. This makes itpossible to distribute these functions or applications over the multipledisciplines of a service provider and use different operating systems,different databases, and different programming languages. In the TMNarchitecture, the element management layer is the only low-levelinterface to the network elements, but needs to give the higher layerssmooth access to information about the network elements.

Background: CORBA

[0020] One important component of the software architecture for moderntelecommunications has been the object-oriented software relationsdefined by CORBA (Common Object Request Brokered Architecture). Thisstandard is particularly useful in telecommunications, where it providesa basic framework for interfacing between element management functionsand other functions (e.g. network management software and systemmanagement software functions).

Background: Optical Telecommunications Standards and Terminology

[0021] The role of telecommunications network management is changing dueto new requirements for speed, increased bandwidth, and capacity tocarry video, digital, and internet data. To provide the neededfunctions, protocols such as ATM, SONET, and SDH are emerging. Networkmanagement systems must accommodate these new technologies andstandards.

[0022] The demand for bandwidth has driven many service providers to useoptical communication systems. A typical set of standards for opticalsynchronization and interconnectivity is SONET (Synchronous OpticalNetwork). SONET is a family of fiber-optic transmission rates designedto transport many digital signals with different capacities and toprovide a design standard for manufacturers. These design standardsprovide an optical interface that allows interoperating of transmissionproducts from different multiple vendors, supports new broadbandservices, and allows enhanced OAM&P (Operations, Administration,Maintenance, and Provisioning).

[0023] SONET has a base rate of 51.84 Mbps, with higher rates beingmultiples of the base rate. The architecture has four layers, theselayers being topped by ATM (Asynchronous Transfer Mode) layers. Thephotonic layer is the physical layer and includes specifications for thefiber optics, transmitter characteristics (such as dispersion of thetransmitter), and receiver characteristics (such as sensitivity). Thesection layer converts electric signals to photonic signals and createsSONET frames. The line layer performs functions such as synchronization,multiplexing of data to SONET frames, switching, etc. The path layerperforms end to end transport of data.

[0024] Open Systems Interconnection (OSI) is an internationally acceptedframework for communication standards between different systems made bydifferent vendors. The OSI model is designed to create an open systemnetworking environment where any vendor's computer system can freelyshare data with other systems on the network. The model organizes thecommunication process into seven different categories and places thesecategories in a layered sequence based on their relation to the user.Layers 7-4 deal with end to end communications, and layers 3-1 deal withnetwork access.

Element Management System with Tree-Structured Representations

[0025] The present inventors have realized that, in this era ofincreasingly larger networks of increasingly more complex networkelements, the old paradigm of network element programming is becomingless appropriate. Where a common change is required to multiple networkelements, previous element management systems have required operators torepetitively make the change to one element after another. This is notonly tedious, but also slows the response time.

[0026] The present application describes a network element managementsystem in which network elements can be grouped, and viewed andmanipulated by groups. This provides both greater ease of use and fasterresponse.

BRIEF DESCRIPTION OF THE DRAWING

[0027] The disclosed inventions will be described with reference to theaccompanying drawings, which show important sample embodiments of theinvention and which are incorporated in the specification hereof byreference, wherein:

[0028]FIG. 1 shows NETSMART connectivity to NEs.

[0029]FIG. 1a shows a network management diagram with vendors usingvendor specific or standard interfaces to communicate with amulti-vendor network.

[0030]FIG. 1b shows the typical layer architecture for management oftelecommunication networks.

[0031]FIG. 2 shows NETSMART window layout.

[0032]FIG. 3 shows NETSMART topology with drop-down file menu.

[0033]FIG. 4 shows the filter dialog, a sample of NETSMART dialogelements.

[0034]FIG. 5 shows the topology manager (with NEs created).

[0035]FIG. 6 shows the topology search NE dialog.

[0036]FIG. 7 shows the result of selection using the search NE dialog.

[0037]FIG. 8 shows the link report in the topoloigy manager/

[0038]FIG. 9 shows OC-192 2F-BLSR.

[0039]FIG. 10 shows the configuration of the equipment tab view.

[0040]FIG. 11 shows the configuration of the properties view.

[0041]FIG. 12 shows the systemadministration view from theadministration manager window.

[0042]FIG. 13 shows the address mangement view from the administrationmanager window.

[0043]FIG. 14 shows the all-view of the address list.

[0044]FIG. 15 shows the NEU management view.

[0045]FIG. 16 shows the concept of installing generics from a localmachine.

[0046]FIG. 17 shows installation of generics from a remote machine.

[0047]FIG. 18 show sthe remote memory backup and restore window.

[0048]FIG. 19 shows the crossconnects: DSO XC tab.

[0049]FIG. 20 shows the crossconnects: FASTLANE XC tab.

[0050]FIG. 21 shows the crossconnects: SONET XC tab.

[0051]FIG. 22 shows the crossconnects: SONET XC tab hairpinning view.

[0052]FIG. 23 shows the crossconnects: SONET XC tab.

[0053]FIG. 24 shows the crossconnects: crossconnect report.

[0054]FIG. 25 shows the crossconnects: DSO XC tab.

[0055]FIG. 26 shows the managing facilities dialog.

[0056]FIG. 27 shows the interface tab: INA attributes view.

[0057]FIG. 28 show sthe PM element view (from NETSMART menu): monitorstab.

[0058]FIG. 29 shows the performance manager elelemt view—registers tab.

[0059]FIG. 30 shows the performance manager element view—database tab.

[0060]FIG. 31 shows the performance manger equipment view.

[0061]FIG. 32 shows the performance manager groups/facilities view.

[0062]FIG. 33 shows the crossconnect report dialog (by crossconnecttype).

[0063]FIG. 34 shows the architecture components of NETSMART.

[0064]FIG. 35 shows the NETSMART process architecture.

[0065]FIG. 36 shows the a hardware architecture for one embodiment ofthe present application.

[0066]FIG. 37 shows the NETSMART server architecture.

[0067]FIG. 38 shows a meta model class diagram.

[0068]FIG. 39 shows a meta base assembly class diagram.

[0069]FIG. 40 shows a meta base assembly state transition diagram.

[0070]FIG. 41 shows a meta node class diagram.

[0071]FIG. 42 shows a meta assembly loading diagram.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0072] The numerous innovative teachings of the present application willbe described with particular reference to the presently preferredembodiment (by way of example, and not of limitation).

Overview of NETSMART®

[0073] NETSMART is a true carrier-class network management systemcapable of managing very large Fujitsu-based SONET deployments whilesimultaneously supporting many active users. NETSMART helps build abusiness by providing the tools to monitor, provision, and troubleshootthe network with unprecedented scalability, graphical interfacesimplicity, and reliability. As with other user-friendly networkmanagement software products, the NETSMART system has an easy-to-use,intuitive graphical user interface (GUI) that allows the user to displaya hierarchical view of the network down to the shelf and card level.NETSMART will also permit the user to obtain graphical control oversurveillance, provisioning, software download (SWDL), remote memorybackup (RMBU), and remote memory restore (RMR). This feature-richinterface allows the user to perform operational tasks without enteringdata or TL1 commands. Point and click operations allow the user toaccomplish the vast majority of all tasks without typing.

[0074] The NETSMART system runs on SUN® Enterprise servers sized to meetsystem requirements. It supports Fujitsu's FLM add/drop multiplexers,FACTR® universal transport and access platform (all the way down to DS0level), FLASH™-192 lightwave add/drop multiplexers, and FLASHWAVEwavelength division multiplexer (WDM).

[0075] NE Support

[0076] NETSMART supports many earlier NE releases. For those NEs notdirectly supported by this version of NETSMART, NETSMART also providesbackward and forward NE compatibility.

[0077] Backward compatibility allows NETSMART to manage an NE as if itssoftware were at a higher release level than it actually is.

[0078] Forward compatibility allows NETSMART to manage an NE as if itssoftware were at a lower release level than it actually is.

[0079] NETSMART also provides Fujitsu Generic Support (FGS) for unknownFujitsu NEs. FGS includes:

[0080] Login/logoff

[0081] Receive, store, and display alarms

[0082] Display of generic NE icon on the Topology Display

[0083] Allow/inhibit alarm reports

[0084] NETSMART Features

[0085] NETSMART combines the functions of both the element managementand network management layers of the Telecommunications ManagementNetwork model to provide comprehensive management capabilities to theusers of Fujitsu networking products.

[0086] General Application Features

[0087] NETSMART provides the following general application features aspart of a comprehensive and robust element and network managementsolution:

[0088] Management of up to 4000 NEs from a single server platform

[0089] Support for OSI DCN connectivity

[0090] TL1 command line and batch file support

[0091] Generic NE icon capability

[0092] Distributed and scalable architecture

[0093] Support for up to 50 simultaneous users

[0094] Support for IP DCN connectivity

[0095] TL1 console allows users to monitor TL1 communication between theNETSMART server and one or more managed NEs

[0096] Intelligent uninterrupted power supply (UPS) support for greatlydecreased start-up times after power failure and for enhanced protectionfrom file system corruption

[0097] Configuration Management

[0098] NETSMART provides the following configuration management featuresto support easy and rapid provisioning and inventory management for bothindividual NEs and entire transport networks.

[0099] Flexible Topology Management

[0100] Topological link and physical link views

[0101] User-defined groups of NEs with the ability to easily move NEsbetween groups

[0102] Tree-widget view of groups, similar to Windows® Explorer,allowing easy viewing and manipulation of managed NEs

[0103] Tabular view of network information

[0104] Comprehensive Network Element Management

[0105] NE definition, profiles, and configuration autodiscovery

[0106] Add user-defined NE or group attributes

[0107] User-defined NE audit and reconciliation

[0108] Select autonomous messages to be allowed upon NETSMART login

[0109] Manual or automatic database reconciliation; option to update NEor NETSMART.

[0110] NE shelf display with visual indications of equipment states

[0111] GUI-based provisioning of attributes and services states forshelves, plug-in units, and facilities

[0112] GUI-based cross-connect management, providing comprehensivemanagement tools, including redline, DSO, hairpinning, FASTLANE™, andtransmux cross-connect management

[0113] Toolbar shortcuts (1-way, 2-way, 2-way add/drop, 1-way drop andcontinue, 2-way drop and continue)

[0114] Bulk cross-connect operations

[0115] Ability to assign a name to cross-connects

[0116] DWDM wavelength management reports

[0117] Network element software management

[0118] Remote NE software upgrades via OSI DCN

[0119] Remote NE database backup and restoration via OSI DCN

[0120] Ability to restore database to a different NE for rapid NEturn-up

[0121] Remote NE software upgrades via IP DCN (FLASH-192 Release 4.2 andFLM 2400 Release 14.2BS only)

[0122] Remote NE database backup and restoration via IP DCN (FLASH-192Release 4.2 and FLM 2400 Release 14.2BS only)

[0123] Full-Featured Network Inventory Management

[0124] Network wide inventory of NEs, shown in FIG. 5: TID, NE type,release level, audit state, DCN type.

[0125] NE level inventory reports: CLEI code, part number, equipmentservice state, date of manufacture, etc.

[0126] Equipment find function: Network-wide search for CLEI code orpart number

[0127] Fault Management

[0128] NETSMART provides the following network surveillance andtroubleshooting features to allow fast and reliable tracking of networkalarms and to provide network operators with tools to quickly and easilyisolate network troubles.

[0129] Network Surveillance

[0130] An alarm banner at the top of the Topology window containingsummary alarm counts and one-click access to alarm reports

[0131] An active alarm list containing current alarms, standingconditions, alarm acknowledgment information, and alarm recordannotations

[0132] An alarm history log showing cleared alarms and cleared standingconditions.

[0133] A transient condition log maintaining records of transientcondition alarms (TCAs) received from managed NEs.

[0134] and transient conditions

[0135] Alarm-sensitive topology map and shelf views

[0136] Audible alarm indications

[0137] Customized alarm viewing options allowing user-defined sorting,filtering, column display/placement, and report layout

[0138] One-click navigation from alarm record to Shelf view.

[0139] Network Troubleshooting

[0140] Protection switch operation and release

[0141] Facility loopback operation and release

[0142] STS path trace

[0143] DWDM section trace for the detection and isolation of errorsbetween DWDM fiber facilities

[0144] Performance Management

[0145] NETSMART provides the following performance management (PM)features to support rapid and accurate detection, isolation, andcorrection of network performance problems:

[0146] Enabling and disabling performance measurement collection fromthe NETSMART GUI

[0147] Collection of both equipment- and facility-related measures witha 15-minute resolution

[0148] Selection and display of PM information through customizedNETSMART reports

[0149] Printing and storage to external files through the NETSMART GUI

[0150] Security Management

[0151] NETSMART provides the following security management features,which allow quick and accurate administration of user privileges whileensuring robust operation within a secure network operationsenvironment.

[0152] GUI-based functional user profile management allows thecustomizing of roles through the combination of individual applicationfeatures.

[0153] Common user roles, such as server admin, client admin,cross-connect user, and alarms user are predefined and available out ofthe box.

[0154] GUI-based user account management, including the ability toenable and disable accounts either on an on-demand or scheduled basis,are provided.

[0155] Comprehensive security reporting, including reports listingdefined users, users with active sessions, and historical user activityis provided.

[0156] Platform Requirements

[0157] The recommended platform configurations for NETSMART 1.2.2 are:

[0158] The server should be sized (CPU and memory) to meet applicationrequirements (number of NEs, number of users) with an even number ofCPUs and with 2 GB of memory for each pair of CPUs.

[0159] The disk size, tape and monitor can vary.

Detailed Description of NETSMART

[0160] NETSMART is the next-generation network element managementsoftware application for the Fujitsu FLM, FACTR®, and FLASH® productlines. In addition, Fujitsu network elements (NEs) that are not fullysupported by NETSMART, but conform to a set of basic TL1 commands, areminimally supported for alarm and configuration purposes. The NETSMARTclient/server configuration supports up to 25 simultaneous users.Further details can be found in the NETSMART 1.2 Installation andAdministration Guide (FJTU-320-940-150) and NETSMART 1.2 Users Guide(FJTU-320-940-100), both of which are hereby incorporated by reference.

[0161] The graphical user interface (GUI) allows:

[0162] Display and update of network topology

[0163] Creation of uniquely named NE nodes, groups of NEs, and links

[0164] Propagation of alarms to network topology icons

[0165] Management of NE configurations, including cross-connects

[0166] Monitoring of alarms

[0167] Performance of troubleshooting procedures

[0168] Execution of remote NE memory backup and software downloads

[0169] Management of user security

[0170] Retrieval of performance management reports

[0171] Wavelength management

[0172] NETSMART is designed to operate on a dedicated Sungserver/workstation. The application uses the TL1 Operational SupportSystem (OSS) language over an Open Systems Interconnect (OSI) protocolstack to communicate with remote NEs. Management of NEs is accomplishedover a combination of wide area networks (WANs), local area networks(LANs), and data communications channels (DCCs), as shown in the exampleconfiguration, FIG. 1.

[0173] Network Elements Supported

[0174] NETSMART software supports Fujitsu NE releases at three differentlevels:

[0175] Full Support: All NETSMART functions are available.

[0176] Forward-Compatible Support:

[0177] Download forward-compatible release level to the NE

[0178] Log on and maintain a session with the NE

[0179] Monitor alarms from the NE (new alarm types may not berecognized)

[0180] Display the shelf view of the NE

[0181] Provision the NE capabilities that were available in the previousrelease

[0182] Perform remote memory backup and restore (if the NE supports it)

[0183] Support other features previously supported

[0184] Backward-Compatible Support: NETSMART treats an earlier releaseof an NE as the immediate later major release and processes autonomousmessages and command responses as if they were from the more recentversion of the NE. Commands that cannot be carried out by the earlierrelease would be denied, but NETSMART would continue to function.

[0185] Using NETSMART

[0186] The following section describes:

[0187] The common desktop environment (CDE);

[0188] How to start the NETSMART™ application on a server and a client;

[0189] How to log on and off;

[0190] How to turn off the workstation.

[0191] Common Desktop Environment

[0192] The CDE is a basic component of the Sun UNIX platform andprovides access to start and stop the desktop applications, one of whichis NETSMART. The CDE toolbar is located at the bottom of the computerscreen. The server CDE toolbar has the Heartbeat icon on the left thatprovides access to administration type functions. These functions arecovered in the NETSMART Administration and Installation Guide. To learnabout the various applications available through the toolbar, access theHelp menu by clicking the books and question mark icon next to the trashcan icon. Several topics display that explain the CDE and itsapplications.

[0193] NETSMART User Levels

[0194] Three levels of NETSMART users are defined:

[0195] System Administrator—is the top-level UNIX operator. The SystemAdministrator is responsible for loading the NETSMART software onto theserver and other related tasks.

[0196] NETSMART User Administrator—is the top-level NETSMART operator.The NETSMART User Administrator has all NETSMART privileges within theapplication, including the ability to create other NETSMART useraccounts.

[0197] NETSMART User—is the operator-level user. The rights of theseusers are defined by a role description, which is classified by theNETSMART User Administrator. For example, an Alarms User is restrictedto using only those commands related to responding to alarms. This userwill not be allowed to perform cross-connects.

[0198] Starting the NETSMART Application

[0199] A central station called the server runs the NETSMART serverapplication and, optionally, the client user interface(s). AfterNETSMART is started on the server, it can be started on the client(s).Each client can perform functions independently of the other clients.Running NETSMART on a client has the following effects:

[0200] Only the client initiating the request will receive a response.

[0201] Autonomous alarms sent from the NE will be received by allworkstations.

[0202] Depending on the user security level, a user can configure NEs;however, only one user at a time can access the following functions: logon an NE, log off an NE, add NE, delete NE, software download, and NEsecurity.

[0203] NETSMART automatically logs on the NEs defined as autologonbefore the user logs on NETSMART. As each NE is logged on, its alarmstatus is downloaded to NETSMART.

[0204] Exiting the NETSMART Application

[0205] Exiting NETSMART closes the NETSMART user interface softwareprogram. The network is not affected and the NETSMART server willcontinue to monitor the network. Normally NETSMART runs continuously onthe Sun workstation. However, if it becomes necessary to turn off theserver, shutdown procedures are included in the System Administrationand Installation Guide.

[0206] The NETSMART™ user interface allows quick identification of andresponse to alarm conditions in a monitored network. The system useswindows and a mouse to minimize keyboard use and training requirementsfor users.

[0207] NETSMART Window Layout

[0208] The Topology window (FIG. 2) displays after the user has loggedon the NETSMART application. As additional operations are started up,additional windows can be opened, including multiple occurrences of thesame window. Windows can be resized and moved to allow multiple views ofthe network. For example, a shelf that is in an alarmed state can bedisplayed in one window and a listing of related alarms can be displayedin another. FIG. 2 is an example of different element positions in themajor NETSMART windows. The NETSMART window elements are:

[0209] Title bar—The title in the title bar can reflect the top-levelelement, the component, and the federation being viewed or the type ofreport or operation being performed. For example, the topology mapdisplays “NETSMART:federation1:Topology” to reflect the top level ofnetwork elements, the component, and the federation. If the view wasswitched to the DSO XC tab for an NE in the Configuration Manager, thetitle reflects the NE TID, such as “FLM150J.” Log Managers will displaythe type of log, such as “Activity Log.”

[0210] 1. Menu bar—The menu bar wording defines categories of NETSMARTcommands. Clicking and holding down the cursor on a menu word displays adrop-down list of the available commands for that category. Continuingto hold down the button, dragging the pointer to highlight the desiredcommand, and then releasing the button causes the command to startexecuting.

[0211] 2. Toolbar—The toolbar displays the tools, which are commandbuttons that provide quick access to frequently used functions. Forexample, on the Topology window, this area is used for NE logon, NElogoff, deleting an NE, adding a ring, and adding a chain. On theright-hand side of the toolbar are the four alarm condition tools. Thealarm tools display the number of current alarms and will flash if thereare alarms that have not been cleared or acknowledged.

[0212] 3. Tree—In the Topology window, this area displays a hierarchicallist of NEs and groups of NEs. In the Configuration window, this arealists cards or facilities, depending on the selection. In the Securitywindow, this area lists users, roles, or user sessions.

[0213] 4. Graphical area—This area is used to display large graphicalinformation such as network maps, shelf views, icons, or reports. Dialogand message boxes can also be displayed on top of this area.

[0214] 5. Icons—An icon is a graphic representation of an object. Iconsare described in legends that are available on related windows and aredescribed in Appendix A of this document.

[0215] 6. Status bar—The status bar is used to display usefulinformation such as the results of the last command or the currentstatus of the selected NE.

[0216] 7. Scroll bars—Scroll bars can be used to reposition a portion ofthe window when the displayed information exceeds the size of thewindow. Either clicking on an arrow or dragging the scroll button willmove the display.

[0217] NETSMART Window Elements

[0218] Several types of Windows elements may appear in the NETSMARTwindow area when commands are selected. These elements are:

[0219] 1. Dialogs—NETSMART uses dialogs to request information from theuser. After supplying the requested information, click on a commandbutton to execute the command. The Tab and SHIFT+Tab keys move thecursor between entry fields in the box.

[0220] 2. Message Boxes—A message box is displayed to explain why acommand cannot be completed, to inform the user of an action inprogress, or to remind the user of the possible consequences of achoice.

[0221] 3. Command buttons—Such as OK, Cancel, Apply, and Help (locatedacross the bottom of a dialog or message boxes) initiate an immediateaction when chosen.

[0222] 4. Reports—NETSMART can display data about NEs, provisioningparameters, or conditions in a tabular form. Often that data can besaved as a file and/or printed.

[0223] Menu Conventions

[0224] Many NETSMART commands are available from the toolbar or fromNETSMART menus (FIG. 3). There are three types of NETSMART menus:

[0225] Main menu, the horizontal list of command names locatedimmediately below the window title

[0226] Associated drop-down menus for each main menu selection

[0227] Pop-up menus, usually displayed from a mouse right-click action

[0228] NETSMART Dialog Elements

[0229] NETSMART dialog elements are the building blocks that are used onthe base dialog window to add functionality to each dialog. Differentdialogs contain different elements to reflect the particular action(s)to be caused by activating the dialog information.

[0230] Dialog Title

[0231] Most NETSMART dialogs have a dialog title or name displayed inthe top portion of the dialog border. In some instances, the dialogtitle may contain the name of a selected element, rather than a constantsingle title. Other dialogs may have both a constant title and avariable name of a selected element.

[0232] Dialog Entities

[0233] A dialog may contain field labels, data/text entry fields, radiobuttons, check boxes, list boxes, drop-down menus, slider bars, andcommand buttons.

[0234] The data/text entry field is designed for the user to typeinformation.

[0235] Radio buttons are mutually exclusive groups of buttons. Selectingone button in the group will deselect all other buttons in the group.Check boxes are used to indicate one or more choices.

[0236] List boxes display a list of values from which the user canselect a single value or a group of values. Contiguous (adjacent) groupsof values are selected by holding down the SHIFT key while selecting thevalues with the mouse. Noncontiguous groups of values are selected byholding down the CONTROL key while selecting the values with the mouse.

[0237] Drop-down menus are menus that display when a selection is madefrom a list box (FIG. 4).

[0238] Slider bars are used to set levels. For example, the NETSMARTGeneral User Preference dialog uses a slider bar to set the number ofminutes that NETSMART can be idle before the NETSMART application screenlocks.

[0239] Command buttons are located at the bottom of dialog boxes. Theyare used to indicate what action NETSMART should take with theinformation that the user entered in the dialog.

[0240] NETSMART Message Boxes

[0241] NETSMART message boxes are a form of dialog designed to alert theuser to an impending condition that may alter the current state ofNETSMART or NETSMART elements. Message boxes can be one of three types:

[0242] Acknowledgement—displays a message that must be acknowledgedbefore continuing. This is usually a “wake-up” type of message and isnot associated with any potentially system-affecting actions.

[0243] Decision—requires the user to decide how to proceed by selectinga command button.

[0244] In Progress—Displays a message stating that an event is occurringand a moving bar to indicate that the process is still continuing.Closing the message box does not stop the process.

[0245] NETSMART Procedures

[0246] The Topology window displays when NETSMART is started for thefirst time. If no network elements (NEs) have been created, no NEs willdisplay in the Topology window on start-up. FIG. 5 shows Topology withNEs already created.

[0247] Note: Most of the main NETSMART™ windows are accessed through thedifferent software managers. These managers are listed on and accessedthrough the NETSMART menu. Therefore, in the following procedures, therelevant manager is indicated in the first steps. If the proper managerwindow is not open, it can be opened by selecting the NETSMART menuoption and then clicking the appropriate manager option.

[0248] A variety of methods can be used to perform these functions;however, the procedures here are written to offer the most directmethods. References to applicable windows are included in theprocedures. As NEs are created, they are, by default, autodiscovered andlogged on. NEs will not be automatically discovered if the userspecifically deactivates the default Auto Logon field during NEcreation.

[0249] Some dialogs are available from several different manager screensbecause of their general nature. They allow the user to setenvironmental preferences and lock/unlock the NETSMART screens forsecurity purposes.

[0250] Create and Manage NEs

[0251] This section describes how NEs are added, modified, maintainedand deleted in the NETSMART database. Only Fujitsu NEs are supported inthis release and they must have already been physically configured inthe network using either TL1 commands or the FLEXR® interface. FujitsuNEs that are not currently in the supported list, but comply withTelcordia TL1 grammar, are supported as generic NEs for commands such asACT-USER, RTRV-ALM-ALL, and INH-DBREPT-ALL.

[0252] Find NE or Group

[0253] This procedure helps to locate an NE or a group of NEs.

[0254] Add an NE

[0255] This procedure adds an NE definition to the NETSMART database.However, to become active, the NE must already be physically in thenetwork and configured using either the FLEXR interface or TL1 commands.

[0256] Clone an NE

[0257] Use the Clone NE dialog to make a copy of an existing NEdefinition. Make changes to the clone to identify a new NE in thenetwork.

[0258] Edit NE Parameters

[0259] Editing an NE allows changes to be made to some basic NEparameters in the NETSMART database.

[0260] Note: The contents of the User ID and Password fields cannot bechanged for an active NE. If these are to be changed, the NE must belogged off and deleted and added once again with the new User ID andPassword information.

[0261] Delete an NE

[0262] Note: NEs should not be deleted during logon (the NE iconbackground is white). Wait until the server has finished logging on,then proceed with the delete operation. Deleting an NE during logoncould cause the NE to be deleted partially. If the NE is partiallydeleted, you need to restart NETSMART to resolve the problem.

[0263] Deleting an NE logs the user off the NE and removes it from theNETSMART database. Deleting an NE also deletes any links associated withthe NE. The NE is still physically in the network, but is removed fromthe NETSMART database.

[0264] Log On an NE

[0265] The user must log on an NE to perform configuration changes andreceive alarm information. Only NEs that are in an inactive state can belogged on. If this is the first time this NE has been logged on,autodiscovery is invoked (NETSMART communicates with the NE database andloads the configuration information into the NETSMART database). If youselect Auto Logon in the Add NE dialog, the log-on process will start assoon as you click Ok or Apply in the Add NE dialog.

[0266] Log Off an NE

[0267] Logging off an NE ends communications between NETSMART and thisNE, but the NE is still defined in the NETSMART database and isfunctioning in the network.

[0268] Audit an NE

[0269] Auditing an NE compares the information contained in the NETSMARTdatabase with the information stored in the NE. The results of the auditare displayed. When you audit an NE using the following procedure, theAudit/Reconcile level that you set will apply only to this audit. TheAudit level that you set when you created or edited an NE will applyonly when the NE is restarted.

[0270] View the NE State

[0271] The current state of any NE in the network can be viewed.

[0272] Resynchronize an NE

[0273] Database resynchronization ensures consistency between the NEdatabase and the NETSMART database. Resynchronization involvesretrieving the entire database or distinct portions of that databasefrom the NE and comparing this information with that contained in theNETSMART database. Either the NE database or the NETSMART database maybe the master data source, depending on the type of data.

[0274] Resynchronization can be a time and resource intensive process.

[0275] Managing Groups of NEs

[0276] Groups are used to organize NEs and partition the network. Agroup icon can represent one or more NEs or groups of NEs. Thebackground color of the group icon reflects a highest unacknowledgedalarm level of NEs in the group.

[0277] Find a Group of NEs

[0278] Finding a single NE and a group of NEs is accomplished using thesame dialog.

[0279] Add a Group Definition

[0280] A group definition can be created and then a group of NEs can bedefined or moved into the new group.

[0281] Edit Group Parameters

[0282] Editing a group allows the user to change group parameters. Thegroup parent can also be changed either by dragging the group icon undera new parent in the tree area or by typing a new parent name in theParent Group field on the Edit Group dialog.

[0283] Delete a Group Definition

[0284] Note: Deleting a parent group results in deletion of all groupsunder the parent group.

[0285] This selection deletes a group definition from the NETSMARTdatabase. If the group has NEs assigned, a warning is displayed and mustbe acknowledged before the delete is completed. The group icon will beremoved from the topology map and tree structure.

[0286] Use a Different Background Map for Each NE Group

[0287] A different background map can be established for each group ofNEs so that when the group is selected, the NEs will be displayed on anappropriate map. The map file(s) must be in “jpg” format and must beaccessible by the server. The file can be on a server drive, on a CD ROMor on a floppy disk that has been placed in the floppy disk drive (usethe UNIX volcheck command to recognize the floppy disk).

[0288] Search NE Dialog

[0289] The Search NE dialog displays whenever the related Search buttonis selected in another dialog that requires an NE name be provided (forexample, in the Add Link dialog). The following procedure assumes thatyou are currently working in a dialog with a Search button. FIG. 6 showsthe Topology Search NE Dialog.

[0290] Search Group Dialog

[0291] The Search Group dialog displays whenever you click on therelated Search button in another dialog that requires a group name beprovided (for example, in the Add NE dialog). The following procedureassumes that you are currently working in a dialog with a Search button.

[0292] Connect NEs (Links, Chains, Rings)

[0293] Network Elements (NEs) are connected to provide varioustelecommunications services. Connection procedures add information aboutthe different types of connections to the NETSMART database. They do notaffect the NEs and physical network because the work defined in theseprocedures must be completed by on-site field technicians.

[0294] Within NETSMART, a single connection between two NEs is referredto as a physical link. The display of this information on the topologymap is referred to as a logical link. There may be more than onephysical link between two NEs, but it will be displayed as a single lineon the topology map unless the connections form a ring. If a ring isformed using only two NEs, both links are displayed as angled lines,showing as a diamond pattern.

[0295] In NETSMART, a link in one direction only is a unidirectionallink. A link in both directions is a bidirectional link.

[0296] In NETSMART, a connection is fully protected only if there aretwo separate routes and these routes do not share any link. A connectionis partially protected if there are two separate routes but these routesdo share a link.

[0297] Add a Link

[0298] A link represents a physical connection between two NEs,including generic NEs. This procedure adds the link information to theNETSMART database to represent the connections in the network. It doesnot affect the networks.

[0299] Note: The selected group and NE will determine the contents ofthe fields on the Add Link dialog.

[0300] Tasks:

[0301] 1 From the NETSMART Topology window, log on all NEs to beincluded in the link.

[0302] 2 Select Add Link from the Edit menu or select the Link tool fromthe toolbar.

[0303] 3 Using the Search button, select information in the followingfields:

[0304] Group 1—Use this field along with the Search button to select aparent group.

[0305] NE1—Use this field along with the Search button to select an NE.After the NE has been selected, available ports are displayed in theLinkable Termination Ports section of this dialog.

[0306] Group 2—Use this field along with the Search button to select aparent group.

[0307] NE 2—Use this field along with the Search button to select an NE.After the NE has been selected, available ports are displayed in theLinkable Termination Ports section of this dialog.

[0308] Linkable Termination Ports—This field displays a graphicrepresentation of the ports that are available for connection for bothselected NEs. If a connection is already in use, the box is grayed out.If a link needs to be created to a generic NE, the facility (forexample, HS1-1, 1-P) port must be typed into the text field at the topof the Linkable Termination Ports area, followed by a carriage return.

[0309] Under each text field, a set of boxes is displayed. Each boxdisplays the RATE (for example OC3), AID (for example 1P) and twodirection buttons: Tx (Transmit) and Rx (Receive). Direction buttons areused to make the connection. These buttons also indicate if a port isunidirectional or bidirectional. If both Tx and Rx are enabled, the portis bidirectional. If either Tx or Rx is grayed out, the port isunidirectional.

[0310] 4 Make a connection between the NEs using one of the followingmethods:

[0311] To create a unidirectional link from Tx to Rx, click on the Txbutton for a linkable port for the first NE to select it. Then move themouse to the linkable port for the other NE and click on the Rx buttonif it is not grayed out. A line displays showing the link, and the Txand Rx buttons for those ports will be grayed out.

[0312] To create a unidirectional link from Rx to Tx, click on the Rxbutton for a linkable port for the first NE to select it. Then move themouse to the linkable port for the other NE and click on the Tx button.A line displays showing the link, and the Tx and Rx buttons for thoseports will be grayed out.

[0313] To create two unidirectional links for a bidirectional port atthe same time, click in an area in the box outside the Tx or Rx buttonsfor a bidirectional port for the first NE. Then move the mouse to abidirectional port for the other NE and click in an area in the boxoutside the Tx or Rx buttons. A line displays showing the link, and theTx and Rx buttons for those ports will be grayed out.

[0314] Once a link is successfully created, connection lines willindicate link direction(s), as shown in FIG. 7. Additional links can beadded until all connections have been defined.

[0315] Note: To deselect a box or button, click on it.

[0316] 5 If the last connection needs to be removed (and Apply or Ok hasnot been selected), click Undo. If all connections need to be removed,click on Clear All.

[0317] 6 Click Apply to add this link information and leave the Add Linkwindow displayed. Click Ok to add the link information and close the AddLink dialog.

[0318] 7 From the View menu, select Graphical to return to the Topologymap display. The link displays on the topology map.

[0319] Display Link Information

[0320] A link represents a physical connection between two NEs. This isNETSMART database information and may not reflect actual physicalnetwork connections. To display the link information for a single link,double-click on the link or right-click and select Link Report from themenu.

[0321] To display the link information for all the links, from theNETSMART Topology window, select Links Report from the View menu. Thetabular view of the Links report (FIG. 8) displays.

[0322] Note the new features of the Link reports in this release:

[0323] An EditName tool can be used to change a physical link name.

[0324] Multiple selection of rows can be used with the Delete andEditName operations. To select a row on the Link Report, click on therow header (numbered from 1 up to the number of physical linksdisplayed) and the row will become highlighted.

[0325] For multiple selections, two options are available:

[0326] Hold down the SHIFT key and click on the desired rows to select acontiguous set of records.

[0327] Hold down the CTRL key and click on the desired rows to select anon contiguous set of records.

[0328] To view the Display Link dialog for the two NEs in the selectedphysical link, double-click on a row.

[0329] The Link Report toolbar offers the following functions:

[0330] Print Print up to 100 lines of the current information. Refer toPrinting Overview for more information.

[0331] Filter Display a dialog where you can specify criteria to filterthe information in the display. Refer to Filtering Tabular Informationfor more information.

[0332] Sort Display a dialog where you can specify criteria to sort theinformation in the display. Refer to Sorting Information.

[0333] Columns Display a dialog where you can specify information to beshown or hidden. Refer to Setting Column Displays for more information.

[0334] Deselect Deselect any selected rows.

[0335] Reload Update the display with information from the database.

[0336] Delete Delete selected physical links from the database.

[0337] EditName Change the name for selected physical links. Use theEdit Name dialog to type a new link name. Click on Ok to confirm thechange(s).

[0338] Edit a Link Name

[0339] The link name defaults to the format <TID>:<port>:<Tx orRx>::<TID>:<port>:<Tx or Rx> of the connection (for example,FLASH-G:HS1-1:Tx::FLASH-F:HS1-2:Rx). This link name can be changed toreflect user preference.

[0340] Delete a Link

[0341] A link can consist of a number of connections between two NEs.This procedure describes how to select an individual connection within alink before deleting the information from the NETSMART database. Theprocedure does not affect the actual physical connections, so links arereferred to as “topology links.”

[0342] Add a Chain

[0343] Chains use high-speed links to connect terminal and linear NEs.This procedure describes adding the link information to the NETSMARTdatabase. The actual physical connections are not performed using thisprocedure. All NEs that will be included in the chain must be logged on.Generic NEs cannot be included in a chain because the NE type cannot beaccurately determined. An NE at the end of a chain must be configured asa terminal type of NE.

[0344] The Add Chain function is a “best-effort” operation. If two ormore of the NEs specified in the list of TIDs encounter a compatibilityerror during ring creation, a dialog box will display. This dialogreports which links were created successfully and which linksencountered errors. The chain will be displayed as lines between NEs. Toaccess the Add Chain dialog, first display the Topology window, andensure that all NEs targeted for the chain have been autodiscovered.

[0345] When the dialog closes, the chain displays on the Topology map.The corresponding links are added to the NETSMART database. Those linksthat were created will be displayed on the Topology map. For those linksthat generated errors, one or more of the following self-explanatoryerror messages may display:

[0346] The configurations for the specified NEs are not compatible.

[0347] High-speed links already exist between two or more of thespecified NEs.

[0348] High-speed rates are not compatible for two or more of thespecified NEs.

[0349] The directions of the high-speed ports are not compatible for twoor more of the specified NEs.

[0350] The payloads of the high-speed ports are not compatible for twoor more of the specified NEs.

[0351] The port sequences of the high-speed ports are not compatible fortwo or more of the specified NEs.

[0352] Add a Ring

[0353] A ring provides alternative routing in case of a single failurewithin a network. This procedure adds a ring definition to the NETSMARTdatabase. The actual physical connections are not performed using thisprocedure.

[0354] The Add Ring function is a “best-effort” operation. If two ormore of the NEs specified in the list of TIDs encounter a compatibilityerror during ring creation, a dialog box will display, reporting whichlinks were created successfully and which links encountered errors.Those links that were created will be displayed on the Topology map. Forthose links that generated the errors, one or more of the followingself-explanatory error messages may display:

[0355] The configurations for the specified NEs are not compatible.

[0356] High-speed links already exist between two or more of thespecified NEs.

[0357] High-speed rates are not compatible for two or more of thespecified NEs.

[0358] Directions of the high-speed ports are not compatible for two ormore of the specified NEs.

[0359] Payloads of the high-speed ports are not compatible for two ormore of the specified NEs.

[0360] Port sequences of the high-speed ports are not compatible for twoor more of the specified NEs.

[0361] Build a BLSR

[0362] A bidirectional line switched ring provides alternative routingin case of a single network failure as shown in FIG. 9, OC-192 2F-BLSR.The BLSR provides ring protection switching by detecting OC-192line-level failures. Ring protection involves bridging (transmittingidentical traffic on both the working and protection channels) andswitching (selecting traffic from the protection channel instead of theworking channel). In a bridge and switch, the 96 working time slots (1through 96) are bridged onto the 96 protection time slots (97 through192) and transmitted away from the failure.

[0363] Each 2F-BLSR can contain up to 16 nodes, labeled uniquely 0through 15 in the ring. The ring topology table contains the order ofthe nodes in the ring.

[0364] Squelching prevents traffic misconnections during node failure byinserting STS-1 path AIS at the switching nodes into the time slots.Each node on the ring has the identities of the entry and exit nodes forall services passing through the node. The squelch table keeps track ofthese entry and exit points by time slot.

[0365] Only the channels that are added or dropped at the isolated nodesor used for extra traffic need to be squelched. The squelch table has anentry for each STS-1 time slot that the node is terminating or passingthrough and the source and destination node IDs.

[0366] Note: The squelch table may take some time to display because theinformation is retrieved from the NE.

[0367] Add a Node to a BLSR

[0368] Nodes may occasionally need to be added to a BLSR. This procedureadds a node to an existing BLSR definition in the NETSMART database.

[0369] Delete a Node from a BLSR

[0370] Nodes may occasionally need to be deleted from a BLSR. Thisprocedure deletes a node from an existing BLSR definition in theNETSMART database.

[0371] Set/Release Loopbacks

[0372] A loopback tests the transmit and receive capabilities of thefacilities at both remote and local terminals. A loopback test causesthe transmitted signal to be returned to the sending device afterpassing through all or a portion of a data communications link or NE.

[0373] Loopback testing is not available on all NE components. An NEcomponent is a facility, equipment and/or termination point. If the NEcomponent is available, right-click on the NE component in the tree areato display a menu containing Loopback.

[0374] The NE must be placed in a maintenance state before a loopbackcan be performed. Placing an NE in maintenance state is not serviceaffecting. However, once an NE has been placed in a maintenance state,actions performed on that NE may be service affecting (a loopback, forinstance, is service affecting).

[0375] Set and Get a Path Trace

[0376] Path trace is a signal sent on the SONET overhead and is onlysupported at the EML layer. It allows the user to assign a unique pathtrace message to the transmit NE and the destination NE.

[0377] Tracing a path involves assigning the outgoing trace message(TRC) at the transmit NE, assigning the same message for the incomingtrace message (EXPTRC) at the path destination NE, and viewing resultsin the incoming trace (INCTRC). If the message is received correctly,the path trace is successful.

[0378] Note: Path tracing is not available on all NE components.

[0379] Set and Get a Section Trace

[0380] In SONET, the terms section, line and path refer to thesubsections of a route that a signal takes when traveling from origin todestination.

[0381] A section is the segment of fiber between two repeater NEs. It ispossible for a signal to be corrupted or degraded over the span of asection. To troubleshoot a particular section for signal qualityproblems, a test signal can be sent on the section and the returnedsignal is compared to an expected trace. This is the essence of sectiontrace.

[0382] Use the Section Trace window to view and modify the attributesrelated to section trace on a selected facility on an NE.

[0383] Note: Section trace is not available on all NEs.

[0384] Protection Switching

[0385] Protection switching allows a transfer of service between workingand protection facilities or equipment. Protection switching allowsplug-ins to be removed and replaced without affecting traffic. Thisfeature also allows editing of the FFP attributes of facilities andequipment within the optical facility and equipment protection groups.

[0386] Note: Protection switching is not available on all facilities andequipment.

[0387] Synchronize Timing

[0388] Timing attributes that will define the synchronization timingsource for the NE and the facility over which the output clock signal issent, can be set by the user. The synchronization reference can also beswitched to another source. Choices of primary, secondary or internalclock references are available to an NE.

[0389] Note: It is dangerous to set the NE timing reference to internalclock timing reference. NEs using internal clock reference can easilybecome out-of-sync with other NEs.

[0390] Note: Synchronization switching is not available on all NEs.

[0391] Equipment Maintenance

[0392] NETSMART can be used to perform basic maintenance on the NEhardware. These include:

[0393] Adding and deleting a shelf for an existing NE

[0394] Provisioning a plug-in unit

[0395] Modifying equipment parameters

[0396] Creating and deleting equipment protection groups (EPGs)

[0397] Add a Shelf to an Existing NE

[0398] The shelf should be installed on an NE before adding it toNETSMART. A NETSMART user can add or remove shelves from an existing NE.For instance, to add a new Narrowband shelf (NBS) to an existing FACTRNE, NETSMART will need to autodiscover the shelf and its components suchas slots, cards, facilities and cross connects.

[0399] Delete a Shelf from an Existing NE

[0400] A NETSMART user can remove shelves from an existing NE.

[0401] Note: All crossconnects must be removed before a shelf can bedeleted.

[0402] Provision a Plug-In Unit (Put In Service)

[0403] A main shelf for a FLASH-192 (Release 2.1) or a FACTR Commonshelf (CMS) or NBS can have some plug-in slots provisioned. The shelfmust already be installed, but the plug-in does not need to beinstalled. Provisioning can also be accomplished by selecting the cardor port and changing the required attribute to In Service (IS). FIG. 10shows the Equipment Tab View for Provisioning.

[0404] Modify Equipment (Card and Port Attributes)

[0405] Individual cards and ports have attributes that can be modified.These attributes are shown in blue on the Properties window for the cardor port. Values that are displayed in red are critical. Changing acritical value will trigger an automatic resynchronization.

[0406] Tasks

[0407] 1 Log on the NE to be provisioned.

[0408] 2 From the Configuration Manager window, select the Equipmenttab.

[0409] 3 Open the tree. From the tree area, select the card or port tobe modified. The view in the window changes to the Properties view.Otherwise, select the card in the graphical shelf view, then right-clickto display a menu where you can select Display Properties. TheProperties view (FIG. 11) displays.

[0410] 4 Modifiable attributes are shown in red and blue. Black textcannot be changed. In the Value column, click on the selection to bechanged. A button appears to the right of the text. Type or select anoption. Click on the button to display a drop-down list of availableoptions. Select an option from the list. Repeat this step for allattributes that need to be changed for this card or port.

[0411] 5 Click on the Modify tool, or select the Update option from theOperations menu. The Modify Attributes Operation progress dialogdisplays. When it closes, the attributes have been changed.

[0412] Create or Delete an EPG

[0413] Redundant equipment provides a level of protection againstfailure of certain plug-in units. For some types of NEs like FLASH-192s,EPGs can be activated or deactivated using this procedure. For FLM andsimilar NEs, EPG are automatically created and cannot be deleted ormodified.

[0414] Using the Administration Manager

[0415] The Administration Manager provides the ability to:

[0416] View administrative details about a selected NE.

[0417] Manage NE addressing.

[0418] View information about NE use.

[0419] Select Administration Manager from the NETSMART menu to displayadministration management tabs.

[0420] Use the System Administration Tab

[0421] The System Administration tab displays details about thedifferent NETSMART processes that are running on the server. TheNETSMART version that is currently installed and the most recent starttime are shown in the heading.

[0422] Process monitoring can be enabled or disabled.

[0423] System monitoring checks the status of the servers (active orinactive) You would disable monitoring only in extreme cases such as anurgent need for resources. If monitoring is enabled (the defaultsetting) and a server goes down, NETSMART will detect state, and issuesa message and attempts to restart the server. If monitoring is disabledand a server goes down, NETSMART will not detect its state change andwill not issue a message or attempt to restart the server. FIG. 12 showsthe Administration Managerview.

[0424] Administration Manager Set Password Dialog

[0425] From the System menu, select the FTP submenu. There are twocascading selections, Set Password, and Show Password. Select SetPassword to change the password for security protection during an FTPtransmission.

[0426] Use the Address Management Tab

[0427] The Address Management tab provides details about each NE.Information includes the TID, the communications protocol, theoriginating address type and the address.

[0428] All system-resolved or manually created OSI addresses are definedas TARP (Target ID Address Resolution Protocol). All IP addresses aredefined as NETSMART. When the server restarts, all NETSMART addressesare retained; all TARP addresses are lost and must be re-resolved aspart of the login process.

[0429] From the NETSMART System Administration window, select theAddress Management tab (FIG. 13).

[0430] Add an OSI Address

[0431] Every NE in a NETSMART network configuration must have an OSI oran IP address. To enable communications within a ring configuration, thegateway NE must be configured as an IP NE.

[0432] If the NE is not a gateway NE, set an OSI address using thefollowing procedure to configure an OSI NE:

[0433] View an OSI Address

[0434] Use this procedure to view an existing OSI address.

[0435] Add an IP Address

[0436] Every NE in a NETSMART network configuration must have an OSI oran IP address. When enabling communications within a ring configuration,the gateway NE must be configured as an OSI NE. If the NE is not agateway NE, set an IP address for the NE. FIG. 14 shows theAdministration Address List—All View.

[0437] View an IP Address

[0438] Use this procedure to view an existing IP address.

[0439] Delete an IP Address

[0440] Use this procedure to delete an existing IP address.

[0441] Use the NEU Management Tab

[0442] The NETSMART hardware platform being used will support a maximumnumber of NE units (NEUs). When this number is exceeded, the databasemay not function properly. The NEU Management tab provides informationabout this usage, allowing for monitoring and managing network capacity.

[0443] The NETSMART NE Utilization window (FIG. 15) is divided intothree areas:

[0444] The top part of the window contains the window title. The MaxCapacity field shows the maximum capacity of the network. The CurrentUtilization field shows the current NEU count for the network. TheAvailable Capacity field shows how many more NEUs can be supportedwithin this network.

[0445] The Summary portion of the window shows summary information,including the Total Number Of NEs, the number Managed, the numberLogged-in, the number Logged-out and the number Not Managed.

[0446] The total number of NEs is the total count of NEs in the system.This includes NEs that are both managed and not managed. Managed NEs arethose that the NETSMART system is aware of and has management controlover. Logged-in are NEs that are logged in and active in NETSMART.Logged-out are NEs that are logged out and inactive. Not Managed are NEsthat NETSMART is aware of but does not manage or control.

[0447] The Details portion of the window provides detail information,including the NE Type, the NE Weight, Number of NEs of this type in thisnetwork and the NEU Count. The capacity of NETSMART systems is based onNetwork Element Units (NEUs). Each type of NE is assigned an NEU valuebased on the number of objects to be managed.

[0448] Use the NEU Management view to monitor the number of NEUscurrently logged on the system. Once the maximum capacity is reached,the system will deny creation of any new NEs.

[0449] Manage NE Software

[0450] This section provides procedures describing:

[0451] How to download software generics to an NE

[0452] How to perform NE memory backups

[0453] How to restore Service Database files to the NE

[0454] How to activate the software generics

[0455] NETSMART uses an intermediate database called Software Repositoryto store and retrieve generic and service database files. This sectiondescribes procedures you will perform to install and extract softwaregeneric and service database files using the Software Repository.

[0456] About the Software Repository

[0457] The Software Repository is an internal database that NETSMARTmaintains in order to store software generic and service database files.It provides a way to extract files from the database to the file system.It also provides the means to remove generic and service database filesfrom the database.

[0458] The Software Repository works off-line with the NE, so it is notnecessary to log on to the NE to use this component. Once the generic orservice database is installed in the repository, it can be downloaded tothe NE using the Software Download (SWDL) component.

[0459] About Remote Memory Backup and Restore (RMBU)

[0460] Remote Memory Backup and Restore (RMBU) is used to make an NEmemory backup and to restore the backup to the NE, when required. To usethe SWDL and RMBU components, you must log on the NE. See Section RemoteMemory Backup and Remote Memory Restore for details about using thesefeatures.

[0461] An RMBU Scheduler feature lets you schedule RMBU in advance.Scheduling options include weekly, monthly or one-time backups. See theInstallation and Administration Guide, Scheduling Remote Memory Backupsfor NEs for details about using this feature.

[0462] Install Generics

[0463] Generics are software files that are specific to a particular NEand version. To upgrade the NE to a different version, the new versionof the generics must be downloaded to the NE. Generics are supplied byFujitsu Network Communications, Inc. (FNC) and are available to thecustomer:

[0464] On a floppy diskette

[0465] On a CD ROM

[0466] From a local or remote machine, using FTP file transfer

[0467] See the Installation and Administration Guide, Installing NESoftware Generics for procedures on installing software generics from aCD ROM or floppy.

[0468] Install Generics from a Local Machine

[0469] Installing generics from a local machine is a single-step processbecause generics were already copied into the NETSMART client machinefile system. Whether the installation is done using FTP, floppy disk orCD ROM, the NETSMART server copies the generic files into therepository. FIG. 16 illustrates the concept.

[0470] Install Generics from a Remote Machine

[0471] Installing generics from a remote machine is a single-stepprocess. Generics can be directly picked up from the remote machine. Inthe following information, generics are available on a remote machine(where the NETSMART client is not running) that is connected to thenetwork. FIG. 17 illustrates the concept of installing generics from aremote machine. The following are required before installing genericsfrom the Client machine:

[0472] The remote machine must be running with the FTP Server daemonactive.

[0473] You need log on access to the machine.

[0474] You need to know the directory path on the remote machine wherethe generics reside.

[0475] Extract Generics

[0476] If software generics are installed in the software repository,they can be extracted. The local file system can be extracted (where theNETSMART client is running) to any other remote machine where you havelog on access, or can be copied onto a floppy disk or CD ROM fordistribution purposes.

[0477] Remove Generics

[0478] If software generics are installed in the software repository,they can be removed. Be sure to remove the generics from the servermachine.

[0479] Install the Service Database

[0480] You can install the service database files in the softwarerepository for downloading to the NE in extreme cases such as NE memorycorruption. To install the service database files, you need to have avalid set of database files from a previous NE backup created with theRMBU manager. Typically, if a memory backup of the NE has been taken,its service database files are stored in the software repository. It ispossible that these files were extracted to the file system. In thiscase, install the files into the repository to download them to the NE.

[0481] Install from a Remote Machine

[0482] If the service database files are available on a remote machinefile system, they can be installed directly into the softwarerepository. The following are required before installing generics fromthe NETSMART client machine:

[0483] The remote machine must be running with the FTP Server daemonactive.

[0484] You need log-on access to the machine.

[0485] You need to know the directory path on the remote machine wherethe generics reside.

[0486] Extract the Service Database

[0487] If the service database files are installed in the softwarerepository, they can be extracted so that they can be saved on the filesystem or copied onto a floppy disk or CD ROM for distribution purposes.Extract the files to the local file system (where the NETSMART client isrunning) or to any other remote machine where you have log-on access.

[0488] Remove the Service Database

[0489] If the service database is already installed in the softwarerepository on the server machine, it can be removed. Be sure to removethe service database, as others (those using NETSMART servers) may wantto use the machine.

[0490] Software Download

[0491] SWDL is used to download new generic software releases (softwaregenerics) onto an NE using File Transfer Access and Management (FTAM)and FTP. As a precondition for SWDL, the generic should be installed inthe Software Repository. For details about installing the generic on theSoftware Repository, refer to Install Generics for more details.

[0492] During the Software Download process, files are copied to the RAMDisk on the NE in the first step and then onto the CPUs. There are threedifferent categories of NEs.

[0493] OSI NEs

[0494] IP gateway NE

[0495] IP subtending NEs.

[0496] Software Download on an OSI NE

[0497] The SWDL to Open Systems Interconnect (OSI) NEs is accomplishedin the following way.

[0498] The files are copied to the RAM Disk on the NE and then the filesare copied to the standby memory of the NE, or

[0499] Files are copied from Network Management System (NMS) to the RAMDisk on the OSI NE using FTAM (for IP gateway NEs this is done usingFTP). At this stage, the software download is in a pending state; itwill become active when the software is activated. For activationinformation, refer to “Configuring Scheduled Remote Memory Backups”.

[0500] Software Download on IP Gateway NE

[0501] SWDL on an IP gateway NE is accomplished in the same way as theOSI NE.

[0502] Software Download on IP Subtending NE

[0503] For subtending NEs, an IP gateway NE is used as a pass-throughfor the files to be copied from the NMS to the destination NE. Theprocedure is accomplished in three steps.

[0504] 1. The files are copied from NMS to the IP gateway NE RAM Disk.

[0505] 2. Then files are copied from the gateway NE RAM Disk onto the IPsubtending NE RAM Disk.

[0506] 3. Finally, files are copied from the subtending NE RAM Disk tothe corresponding CPUs on the IP subtending NE.

[0507] Consecutive Operations

[0508] From a user perspective, software download can be initiated onlyon a single NE at a time. Initiating software download on several NEs atthe same time is not supported; however, you can start software downloadon different NEs, running one after another. Software download cannot beinitiated on any NE while the NE is performing a remote backup or arestore.

[0509] For IP subtending NEs, an IP gateway NE is used as a pass-throughfor copying the files. An IP Gateway NE can be a gateway for severalNEs, meaning that all the NEs under this gateway NE are dependent onthis gateway NE for software management operations.

[0510] Details Dialog

[0511] Once an NE is selected from the Software Download dialog and thedownload is started, you can monitor the download. Select the Detailsdialog by clicking the Details button in the Software Download dialog.

[0512] The Details dialog displays the number of files to be transferredin each step and also the number of files currently transferring. Statusstrings on the Details dialog help you to understand the operation.

[0513] An important string called Failure Reason is displayed on theDetails window if the SWDL is aborted. The failure reason will help youto understand why the SWDL failed.

[0514] Abort Operation

[0515] After SWDL is started, the Software Download can be aborted.Select the Abort button to display a status string on the SWDL window,indicating that the abort has initiated. It may take several minutes forthe abort operation to be completed, depending on the stage of the SWDL.

[0516] Once the abort is completed, the status string contents willchange to inform the user that the abort has completed. The message willprovide the time of the abort. You can now schedule an activation andset the validation time. For more details about activation, refer to“Configuring Scheduled Remote Memory Backups”.

[0517] Remote Memory Backup

[0518] Remote memory backup (RMBU) backs up the configuration databaseon an NE to the NETSMART database. At any time, only the last twoversions of backup (per NE) are stored in the database. The backed-up NEconfiguration information can either be extracted onto any machine (withan active FTP daemon) or can be restored from the NE database. Refer toExtract the Service Database for details about extracting backed-upfiles onto a remote machine. Refer to Remote Memory Restore for detailsabout restoring the NE database.

[0519] During the backup process, files are copied from CPUs to NE RAMDisk. There are three different categories of NEs.

[0520] OSI NEs

[0521] IP gateway NE

[0522] IP subtending NEs

[0523] Remote Memory Backups from an OSI NE

[0524] A remote memory backup from an OSI NE is accomplished in thefollowing way:

[0525] The configuration files are copied to the RAM disk on the NE fromactive memory.

[0526] The files are copied from the NE's RAM disk to NETSMART using theOSI FTAM protocol.

[0527] Remote Memory Backup from an IP Gateway NE

[0528] A remote memory backup from an IP gateway NE is accomplished inthe following way:

[0529] The configuration files are copied to the RAM disk on the NE fromactive memory.

[0530] The files are copied from the NE's RAM disk to NETSMART using theFTP protocol.

[0531] Remote Memory Backup from an IP Subtending NE

[0532] A remote memory backup from an IP subtending NE is accomplishedin the following way:

[0533] The configuration files are copied to the RAM disk on the NE fromactive memory.

[0534] Using the OSI FTAM protocol, the configuration files are copiedfrom the subtending NE's RAM disk to its gateway NE's RAM disk.

[0535] The configuration files are then copied to NETSMART using the FTPprotocol.

[0536] Concurrent Operations

[0537] Backup can be initiated on up to 100 NEs. These NEs include OSINEs, gateway NEs and IP subtending NEs. If backup is initiated on an IPsubtending NE, this operation locks its gateway NE and transfers filesthrough the gateway NE. If backup is initiated on multiple NEs within aring, the gateway NE is shared across these backup operations.

[0538] At any time, backup for 10 NEs can be initiated in parallel. Ifbackup for more than 10 NEs is requested, backups are serialized.

[0539] During either of the SWDL/RMR (Remote Memory Restore) operationson a gateway or subtending NE, you cannot initiate a backup on any ofthe NEs in that ring. If the NE database is being restored onto agateway NE or a subtending NE, a backup cannot be initiated on any ofthe NEs in that ring.

[0540] Details Dialog

[0541] The Details dialog displays the number of files to be transferredin each step and also the number of files currently transferring. Statusstrings on the Details dialog help you to understand the operation.

[0542] An important string called Failure Reason is displayed on theDetails window if the SWDL is aborted. The failure reason will help youto understand why the SWDL failed.

[0543] Abort Operation

[0544] You can select an NE and click the AbortBkp tool. Status messagesfor this NE indicate initiation and completion of the abort operation.FIG. 18 shows the Remote Memory Backup and Restore Window.

[0545] Remote Memory Restore

[0546] If database corruption occurs on an NE, remote memory restoreallows a previously stored configuration database for that NE to beused. The configuration files for an NE are stored either from thebackup operation or by installing NE database files from a remotemachine (with the FTP daemon running). Refer to Remote Memory Backup fordetails about backing up NE configuration files from an NE. Refer toRemote Memory Restore for details about installing these files.

[0547] Log on the NE to be restored. During the restore process, filesare copied from NMS to NE RAM Disk and then onto CPUs. There are threedifferent categories of NEs.

[0548] OSI NEs

[0549] IP gateway NE

[0550] IP subtending NEs

[0551] Remote Memory Restore to an OSI NE

[0552] A remote memory restore to an OSI NE is accomplished in thefollowing way:

[0553] The configuration files are copied from NETSMART to the NE's RAMdisk.

[0554] The configuration files are copied from the RAM disk on the NE tostandby memory.

[0555] An activation of the standby memory needs to performed. Refer toSoftware Activation for information on software activation.

[0556] Remote Memory Restore to an IP Gateway NE

[0557] A remote memory restore to an IP Gateway NE is accomplished inthe following way:

[0558] The configuration files are copied from NETSMART to the NE's RAMdisk using the FTP protocol.

[0559] The configuration files are copied from the RAM disk on the NE tostandby memory.

[0560] An activation of the standby memory needs to performed. Refer toSoftware Activation for more information on software activation.

[0561] Remote Memory Restore to an IP Subtending NE

[0562] A remote memory restore to an IP subtending NE is accomplished inthe following way:

[0563] The configuration files are copied from NETSMART to the gatewayNE's RAM.

[0564] The configuration files are copied from the RAM disk on thegateway NE to the RAM disk on the subtending NE using the OSI FTAMprotocol.

[0565] The configuration files are copied from the RAM disk on thesubtending NE to standby memory.

[0566] An activation of the standby memory on the subtending NE needs toperformed. Refer to Software Activation for more information on softwareactivation.

[0567] Consecutive Operations

[0568] A restore can be initiated on only one NE at a time. If anysoftware management operation is running on any NE in a ring, you cannotinitiate a restore operation on any of the NEs in that ring.

[0569] Backup Details Dialog

[0570] The Details dialog displays the number of files to be transferredin each step and also the number of files currently transferring. Statusstrings on the Details dialog help you to understand the restoreoperation. An important string called Failure Reason is displayed on theDetails window if the restore operation is aborted. The failure reasonwill help you to understand why the restore failed.

[0571] Abort Backup Operation

[0572] While the restore process is active, you can select an NE andclick on the AbortBkp tool to abort the backup process. Status messagesfor this NE indicate initiation and completion of the abort operation.

[0573] Software Activation

[0574] After the generic or database is loaded into memory, you need toschedule an activation.

[0575] Note: When activating either a software download or a remotememory restore, activation time can be selected based on the NE time.NETSMART reads the time from the TL1 response and places the NE timeplus 2 minutes in the Time field. This is to prevent the SWDL or RMRactivation time from being the exact current time. If this was the case,by the time the user finished selecting activation time, the time wouldnow be in the past.

[0576] Managing Crossconnects

[0577] This section provides the procedures for creating NEcrossconnects. Crossconnect commands perform changes to the network andupdate the NETSMART database. NE crossconnect management provides theability to modify the route for a circuit by changing the NEs and linkswhere a signal is carried. NETSMART's graphical crossconnection featurelets you create crossconnects using a mouse click interface and lets youview and report on an end-to-end circuit through a SONET network.

[0578] Circuits may span multiple NEs and multiple interconnected ringsand virtual rings. You can select the appropriate pass-through,drop-and-continue and service selector to assign.

[0579] Pending, active and errored connection states are supported. Apending connection state is one in which the crossconnects associatedwith a connection are defined in the database, but have not beenconfigured in the NEs. In an active connection, the crossconnectsassociated with a connection are defined in the database and alsoconfigured in the NEs. An errored connection exists when there is adiscrepancy between the definition of the connection in NETSMART and theactual crossconnects in NEs.

[0580] Crossconnect windows can be accessed from the ConfigurationManager or by selecting Crossconnect Manager from the NETSMART menu. Thecrossconnect windows all bear the title “Configuration”.

[0581] Add a DSO Crossconnect

[0582] Use this procedure to create redline and regular DSOcrossconnects that drop off from the FACTR low-speed group (Group 3, 4,and 5) feeder to the Remote Digital Terminal (RDT) interface/NBS. T1crossconnects are created using the procedure found in Add a T1Crossconnect, below.

[0583] If the interface group is Integrated Network Access (INA) orTR-008 Mode I or III, the next available DS0 time slot will bepresented. If the interface group is TR-303 or TR-008 Mode II, the nextCall Reference Value (CRV) number will be presented, and can beoverridden. NETSMART determines the DSO facility AIDs and sends theappropriate TL1 commands. FIG. 19 shows the DSO XC crossconnect tab.

[0584] Add a T1 Crossconnect

[0585] Use this procedure to create the redline and regular DS1 feederside of an interface group and the T1 facility in the FACTR low-speedgroup (Groups 3, 4, and 5) feeder for DS0 services.

[0586] Crossconnects are limited by the following types of interfacegroups:

[0587] TR-008 (Mode I)—Choose an available feeder DS1 (A, B, C, or D).

[0588] TR-008 (Mode II or III)—Choose an available feeder DS1 (A or C).

[0589] TR-303—Choose an available DS1 (1 through 28).

[0590] INA—The T1 crossconnects are automatically created between thefeeder of the INA interface group and the VT1 of the low-speed groupwhen the first DS0 crossconnect is created. You cannot create them, butthey can be displayed.

[0591] Tasks:

[0592] 1 Log on the NE to be crossconnected.

[0593] a. If Crossconnect Manager was selected from the NETSMART menu,the Configuration window displays. In the Configuration window, selectthe DS0 XC tab.

[0594] b. If the crossconnect needs to be a redline, click the Redlinetool or select Redline from the Create XC selection on the Operationsmenu.

[0595] c. Click on the DS1 box to be connected, then drag the line tothe port and click again. A dotted black line appears.

[0596] Note: If the interface group or port (rectangle) is yellow, thenit is already in use (possibly at a different speed).

[0597] d. To complete the connection, click the Update tool or selectUpdate NE from the Operations menu. The Confirmation dialog displays

[0598] Add a FASTLANE Crossconnect

[0599] FASTLANE crossconnects are used to map Ethernet and DS3 UNIservices into an STS-1. FASTLANE™ service is only available forfunctional groups 4 and 5 configured as D3U or LAN bridge port (LBP). Atleast one dedicated STS-1 channel across the SONET ring must beavailable to carry the FASTLANE traffic. Two types of FASTLANEcrossconnects are supported:

[0600] Ethernet Port-Mapped Bridge (EPMB)—an entity connecting an EPMBto a ring-side Asynchronous Transfer Mode virtual channel (ATMVC)

[0601] DS3 User Network Interface (D3UNI)—an entity connected to aparticular ATMVC supported by a D3 UNI port to a ring-side ATMVCEthernet port provisioning and ATMVC provisioning are performedindependently of establishing crossconnects. Create ring-side ATMVCs tocreate a path through the network between the switches. The D3 UNI ATMVCports are created by NETSMART. The value is shown for the next availableVirtual Channel Identifier (VCI). You may override that channelselection.

[0602] Tasks:

[0603] 1 Log on the NE to be crossconnected

[0604] 2 If the Crossconnect Manager was selected from the NETSMARTmenu, the Configuration window displays. In the Configuration window,select the FASTLANE XC tab. The Fastlane XC view (FIG. 20) displays.

[0605] 3 Select Create ring VC from the Operations menu or right-clickand select Create Ring VC from the drop-down menu. The Ring VC creationdialog displays.

[0606] 4 Select or type values in the following fields:

[0607] Ring VC VPI (0-0)—Type the Virtual Path Identifier (VPI). Only 0is valid. Ring VC VCI (34-1023)—Type the VCI of the virtual channel.

[0608] PCR—Type the Peak Cell Rate (PCR) per second.

[0609] SCR—Type the Sustained Cell Rate (SCR) per second.

[0610] Congestion Control—Select whether congestion control should beenabled or not.

[0611] AAL-Type—Select the ATM Adaptation Layer (AAL). Only AAL5 isvalid.

[0612] From NE TID—The starting NE TID is the default value.

[0613] T NE TID—Select the ending NE TID from the list.

[0614] 5 Click Ok to add the ring VC and close the Ring VC creationdialog.

[0615] 6 Click Apply to add the ring VC and leave the Ring VC creationdialog displayed.

[0616] 7 Click Cancel to cancel any changes and close the Ring VCcreation dialog. If Ok or Apply was selected, the new VC displays in themiddle of the FASTLANE XC window.

[0617] 8 Click on the appropriate port in the Group Configuration. Onthe FASTLANE XC tab, drag the mouse to the appropriate ring VC, thenclick again. A dotted line(s) will show the connection.

[0618] 9 To complete the connection, click the Update tool or selectUpdate NE from the Operations menu. The crossconnect Confirmation dialogdisplays

[0619] Add a SONET Crossconnect

[0620] A SONET crossconnect connects STS or VT time-slot facilities. ASONET crossconnect can connect a high-speed time slot to anotherhigh-speed time slot (pass-through), a high-speed time slot to alow-speed time slot (add and drop), and a low-speed time slot to anotherlow-speed time slot (hairpinning). Time slot rates must match for allSONET crossconnects.

[0621] Note: For FLASH 192 2.x and 3.x NEs, not all AIDs can beinterconnected. Only those AIDs that fan out from a SONET line that isgreen in color are open for crossconnects.

[0622] Tasks:

[0623] 1 Log on the NE to be crossconnected

[0624] 2 If the Crossconnect Manager was selected from the NETSMARTmenu, the Configuration window displays. In the Configuration window,select the SONET XC tab. The SONET XC view (FIG. 21) displays.

[0625] 3 Select the type of crossconnect (OneWay, TwoWay,OneWayBroadcast, TwoWayDropAndContinue, TwoWayAddAndDrop, or ServiceSelector) from the Create XC option of the Operations menu or byclicking on the corresponding tool. Note: Not all types of crossconnectare available at all times (depending on the NE type and theconfiguration).

[0626] 4 If the crossconnect also needs to be a redline, click on theRedline tool or select Redline from the Create XC option on theOperations menu.

[0627] 5 Click on the first STS or VT1 group to be connected, then dragthe line to the far-end STS or VT1 group and click. A dotted line showsthe connection. If a drop-type connection is required, click on thefirst STS or VT1 group (left- or right-hand side), then click on thedrop port along the bottom of the window and dotted lines will begenerated (including the appropriate right-hand group). Note: The timeslot rates on both ends of this crossconnect must be equal. If thetime-slot rectangle is yellow, then it is already in use (possibly at adifferent speed).

[0628] 6 To complete the connection, click the Update tool or selectUpdate NE from the Operations menu. The crossconnect Confirmation dialogdisplays

[0629] Add a Hairpin Crossconnect

[0630] A hairpin is a crossconnect between two low-speed SONETtermination points.

[0631] Note: Hairpin crossconnects are supported for FLASH XC MVarchitecture. The FACTR or FLM 150 must have a TS1A-ENH2 (time slotassignment) unit, which allows the low-speed crossconnects. The systemtype must be linear or Unidirectional Path Switched Ring (UPSR) and theNE device system parameter TSTYPE must be provisioned as ENH2.

[0632] One-way, 2-way, bridge and roll crossconnects can be created,modified and deleted. Creation and deletion of redline crossconnects issupported. If a crossconnect is redlined, the redline must be removedbefore deletion.

[0633] Tasks:

[0634] 1 Log on the NE to be crossconnected.

[0635] 2 If Crossconnect Manager was selected from the NETSMART menu,the Configuration window displays. In the Configuration window, selectthe SONET XC tab

[0636] 3 Select the Hairpinning option from the Operations menu. TheHairPinning view (FIG. 22) displays.

[0637] 4 Depending on the type of crossconnect, select the One way orTwo way tool or select the corresponding menu option from the Operationsmenu. If the crossconnect also needs to be a redline, click on theRedline tool or select Redline from the Create XC option on theOperations menu.

[0638] 5 Click on the first group to be connected from the From TP line,then drag the mouse to the appropriate group in the To TP group andclick again. A dotted line will appear.

[0639] 6 When all of the crossconnects have been defined, click on theUpdate tool or select Update NE from the Operations menu.

[0640] 7 Verify the connections. If the connections are correct, clickOk. If the crossconnect was created successfully on the NE, the line(s)will change from dashed to solid. If the crossconnect on the NE fails,the crossconnect lines will remain dotted. If connections are notcorrect, click Cancel and then change the connections. The ConfirmConnection dialog displays, indicating the success or failure of thecrossconnect.

[0641] Add a One-Way Service Selector Crossconnect

[0642] The one-way service selector is used for the BLSR configurationfor FLASH-192 and FLM-2400 SONET NEs.

[0643] Tasks:

[0644] 1 Log on the NE to be crossconnected

[0645] 2 If Crossconnect Manager was selected from the NETSMART menu,the Configuration window displays. In the Configuration window, selectthe SONET XC tab. The SONET XC view (FIG. 23) displays.

[0646] 3 Select the One Way service selector tool. Click on thelow-speed port, then click on the destination high-speed port. Thecrossconnect displays as a dotted line. Note: The default ServiceSelector and Holdoff times can be changed at this time by right-clickingon a crossconnect and selecting the appropriate menu item.

[0647] 4 To complete the crossconnect, click on the Update tool orselect Update NE from the Operations menu.

[0648] Perform a Bridge on an Existing Crossconnect

[0649] Bridge crossconnect functionality is supported for BLSRconfigurations of FLASH-192 and FLM 2400 SONET NEs. By setting up abridge, traffic from one termination point is routed to two othertermination points. Bridge and roll operations are performed on two NEsto complete the entire task. First do a bridge on a crossconnect on oneNE and then do the roll on the other NE. After the roll is performed,clear the bridge on the first NE.

[0650] 1 Log on the NE whose path is to be modified.

[0651] 2 If Crossconnect Manager was selected from the NETSMART menu,the Configuration window displays. In the Configuration window, selectthe SONET XC tab. The SONET XC view displays.

[0652] 3 Select the 1-way drop crossconnect to be bridged.

[0653] 4 Click the Bridge tool or select Bridge from the Operationsmenu.

[0654] 5 Select the destination time slot. The display will show the newbridge connection as a dotted line on the window when the operation iscompleted.

[0655] 6 To complete the connection, click the Update NE tool or selectUpdate NE from the Operations menu.

[0656] Perform a Roll on an Existing Crossconnect

[0657] Roll crossconnect functionality is supported for the FLASH-192and FLM 2400 SONET NEs. On an FLM 2400 SONET NE, this functionality isavailable only when the NE is configured as a BLSR. Rolling facilitatesswitching the source AID from one time slot to another time slot withoutloss of signal. Traffic is buffered by the NE during the roll operation.

[0658] The roll operation can be performed by selecting a 1-waycrossconnect and then clicking the Roll tool or by selecting the Rollmenu item from the Operations menu. After you select Roll, rubberbanding starts and you can select a new origination point. A pendingroll crossconnect is created You can then activate the rollcrossconnect, which results in deletion of the original crossconnect andcreation of a new roll crossconnect. Bridge and roll operations areperformed on two NEs to complete the entire task.

[0659] First set a bridge on a crossconnect on one NE and then set aroll on the other NE. After the roll is performed, clear the bridge onthe first NE.

[0660] 1 Log on the NE whose path is to be modified.

[0661] 2 If Crossconnect Manager was selected from the NETSMART menu,the Configuration window displays. In the Configuration window, selectthe SONET XC tab. The SONET XC view displays.

[0662] 3 Select the 1-way crossconnect to be rolled from.

[0663] 4 Click the Roll tool or select Roll from the Operations menu. Aprompt displays directing you to select the destination time slot.

[0664] 5 Select the destination time slot. The display will show the newconnection as a dotted line on the window when the operation iscompleted. The old connection will be displayed as a solid line.

[0665] 6 To complete the connection, click the Update NE tool or selectUpdate NE from the Operations menu.

[0666] Crossconnect Confirmation

[0667] The same dialog displays to confirm all types of crossconnects.

[0668] 1 To complete the crossconnect, click on the Update tool orselect Update NE from the Operations menu. The crossconnect Confirmationdialog displays.

[0669] 2 Verify the connections. If the connections are correct, clickOk. If the crossconnect was created successfully on the NE, the line(s)will change from dashed to solid. If the crossconnect on the NE fails,the crossconnect lines will remain dotted. If connections are notcorrect, click Cancel and then change the connections. The ConfirmConnection dialog displays, indicating the success or failure of thecrossconnect.

[0670] 3 Click the Close button to close the Crossconnect Report. FIG.24 shows the Crossconnect Report.

[0671] Update the Crossconnect Name

[0672] Crossconnects are not given a name when they are created. Thename can be structured to conform to the user's own network namingconvention; however, crossconnect names must be alphanumeric, with nospecial characters. Several crossconnects can be updated at the sametime.

[0673] Note: A crossconnect name must be alphanumeric and cannot containany special characters.

[0674] 1 Log on the NE with the crossconnect(s).

[0675] 2 If Crossconnect Manager was selected from the NETSMART menu,the Configuration window displays. In the Configuration window, selectthe SONET XC tab. The SONET XC view displays.

[0676] 3 Select the crossconnect that needs a new name. Select Set Namefrom the Operations menu, or right-click on the crossconnect and chooseSet Name . . . . The Set Crossconnect Names dialog displays.

[0677] 4 Type a new name.

[0678] 5 Select the Set All button to move the crossconnect name to theCrossconnect Name field in the Set Crossconnect Names dialog. Click Okto close the Set Crossconnect Names dialog.

[0679] 6 The cross-connect displays as a dotted line. Click on theUpdate tool. The Confirmation dialog displays. Verify that theinformation is correct and click Ok.

[0680] 7 The Messages dialog box displays with the new name shown in thetable. Click Ok

[0681] Adding Redline Designation to an Existing Crossconnect

[0682] Adding a redline designation to a crossconnect indicates that itis a critical circuit and care should be taken when changes ordisconnects are issued that affect the crossconnect.

[0683] 1 Log on the NE with the crossconnect(s

[0684] 2 From the Configuration Manager, select the SONET XC tab or DS0XC tab, depending on the type of crossconnect to be redlined. FIG. 25shows the DS0 XC display.

[0685] 3 Select the crossconnect that needs to be redlined. Click theSetRedl tool or select Set Redline from the Operations menu. Multiplecrossconnects can be chosen by holding down the SHIFT and CTRL keys,then clicking on the crossconnect lines. The crossconnect line willchange to a dotted red line.

[0686] 4 To complete the redline designation, click on the Update toolor select Update NE from the Operations menu.

[0687] Delete a Crossconnect

[0688] Most crossconnects can be deleted using this procedure. If thecrossconnect is redlined, the redlining must be removed, as describedthis procedure.

[0689] 1 Log on the NE where the crossconnect is to be deleted.

[0690] 2 If Crossconnect Manager was selected from the NETSMART menu,the Configuration window displays. In the Configuration window, selectthe appropriate tab: SONET XC, DS0, or FASTLANE.

[0691] 3 If the crossconnect is redlined, the redline designation mustbe removed first. Select the crossconnect and click the NoRed tool orselect Unset Redline from the Operations menu. Click on the Update NEtool or select Update NE from the Operations menu. The Confirmationdialog displays.

[0692] 4 Click Ok to remove the redline.

[0693] 5 Click on the crossconnect to be deleted. Multiple crossconnectscan be selected by holding down the CTRL and SHIFT keys and thenclicking on each crossconnect to be deleted.

[0694] 6 Click on the DelXC tool or select Delete XC from the Operationsmenu. The crossconnect line changes from solid to dashed, indicating apending change of state.

[0695] 7 After all crossconnects have been marked for deletion in theGUI, make the changes to the NE by clicking the Update tool or selectUpdate NE from the Operations menu. The crossconnect Confirmation dialogdisplays.

[0696] 8 Verify that the appropriate crossconnects are listed, thenclick Ok to complete the deletion. If the crossconnections are notcorrect, click Cancel and reselect the connections. If you cancel thedeletion, click the Undo tool to reinstate the connection.

[0697] Changing SSDEF

[0698] The Service Selector Definition (SSDEF) is, by default, set toInsert. To reset the SSDEF to Thru, perform the following procedure:

[0699] 1 Log on the NE where the SSDEF is to be reset. Access theappropriate crossconnect window.

[0700] 2 Right-click on a crossconnect to display a menu.

[0701] 3 Select Set SS to Thru. The menu selection Set SS to Thruchanges to Set SS to Insert. You can toggle this selection between thetwo items. Only the inactive selection will display in the menu.

[0702] Changing the Holdoff Timer Value

[0703] The holdoff timer is used to set the time interval after aprotection switch when the NE will check the traffic origin and reset tothat origin if possible. To change the holdoff timer value, perform thefollowing procedure:

[0704] 1 Log on the NE where the holdoff timer is to be set. Access theappropriate crossconnect window.

[0705] 2 Right-click on a crossconnect to display a menu.

[0706] 3 Select Holdoff Timer. Type a value for the reset interval.

[0707] Trace from a Time Slot

[0708] If you are viewing a crossconnect with one termination point, butno crossconnect visible, you can discover the other end of thiscrossconnect.

[0709] 1 Log on the NE. Access the appropriate crossconnect window.

[0710] 2 Right-click to select a crossconnect and display a menu whereyou will choose Trace XC. A label will display beside the crossconnecttermination point where you right-clicked. This label identifies theother end of this crossconnect.

[0711] Manage Facilities

[0712] This section provides the procedures for defining and managingfacilities for FLASH-192, FLM and FLASHWAVE NEs. Primary states forfacilities are: In Service (IS), Out of Service Autonomous (OOS-AU), Outof Service Management or Memory Administration (OOS-MA) and Out ofService Autonomous Management (OOS-AUMA). Facilities can also have asecondary state of Out of Service Management Unassigned (OOS-MA:UAS)when they are manually deleted.

[0713] Facilities can have secondary states of active (ACTI), normal(NR), abnormal (ANR), standby-hot (STBH), supporting entity outage(SGEO), facility failure (FAF), unassigned (UAS), and automatic inservice (AINS).

[0714] Add a Facility (FLASHWAVE or FLASH-192)

[0715] Use this procedure to add fiber facilities for a FLASHWAVE orFLASH-192 NE.

[0716] Note: Facilities cannot be created unless supporting equipmenthas been created.

[0717] Note: When creating or modifying OC-48/OC-192 facilities in aTransponder type of FLASHWAVE NE a message will ask you to providedirectional attribute information. Always input the attributes (UNI orBI, for example) in upper case.

[0718] 1 From any tab in the Configuration Manager, select the ManagingFacilities . . . option from the NE menu. The Managing Facilities dialogdisplays (FIG. 26, Managing Facilities Dialog).

[0719] 2 Click on the rate and select the rate from the Rate drop-downlist. Select the shelf from the Shelf drop-down list. Select thefacility in the Non-existing Facilities column. Click the Create tool.

[0720] Note: If there are no nonexisting (deleted) facilities, therewill be nothing in this list

[0721] 3 If this facility has any key attributes whose value should bespecified at creation time, a dialog containing the key attributes willdisplay. Enter the values for these attributes and click Ok.

[0722] 4 The selected attributes of the selected facility will displayin the Attributes table. Click the Create tool. A Manage Facilitiesmessage box displays: Creating Facilities. The facility will be movedfrom the Non-existing to the Existing column and will be activated.

[0723] Modify a Facility

[0724] This procedure allows you to modify facilities.

[0725] Note: When creating or modifying OC-48/OC-192 facilities in aTransponder type of FLASHWAVE NE a message will ask you to providedirectional attribute information. Always input the attributes (UNI orBI, for example) in upper case.

[0726] 1 From the Configuration Manager, select the Groups/Facilitiestab.

[0727] 2 Select the facility from the expanded tree or from the graphicarea. The Attributes view displays. This display will vary slightly,depending on the command origin (issued from the tree or graphic area).

[0728] 3 Modify the required values shown in blue or red, then click theModify tool or select the Update option from the Operations menu.Available operations include InServ, OOSMA, OOSMT, InServ, Operate PSWand Release PSW (the particular operation(s) available will depend onthe facility). The same options can also be chosen from the Operationsmenu.

[0729] 4 The values will be modified in the NE and the NETSMART databaseDelete a Facility. This procedure allows you to delete facilities for aFLASHWAVE or FLASH-192 NE.

[0730] Delete a Facility

[0731] 1 From any tab in the Configuration Manager, select the ManagingFacilities option from the NE menu. The Managing Facilities dialogdisplays.

[0732] 2 Select the shelf from the Shelf drop-down list. Click on therate and select a rate from the Rate drop-down list. Select the facilityin the Existing Facilities column. Click the Create tool.

[0733] Note: If there are no existing (created) facilities, there willbe nothing in this list.

[0734] 3 A confirmation dialog displays. Click Ok to delete thefacility. The facility will be moved from the Existing Facilities to theNon-existing Facilities column and will be deactivated

[0735] Activate an FFP Group (FLASH-192)

[0736] Fiber Facility Protection (FFP) groups are available forFLASH-192. The equipment and the facilities to support the FFP groupmust already be created. A list of FFP pairs is displayed and you willselect the FFP to be created.

[0737] Note: Changing FFP groups may change system configurations, whichcan cause system configuration inconsistencies.

[0738] 1 From any tab in the Configuration Manager, select the ManageFFP option from the NE menu. The Manage FFP dialog displays.

[0739] 2 Select the shelf from the Shelf drop-down list. Click on therate and select the rate from the Rate drop-down list. Select the FFP inthe Non-existing FFP column.

[0740] Note: The list will be empty If there are no nonexisting(deleted) FFPs.

[0741] 3 Click the Create tool.

[0742] 4 The FFP will move from the Non-Existing FFP to the Existing FFPcolumn and will become active.

[0743] Modify (or View) an FFP Group

[0744] The FFP group attributes for NEs can be modified, by performingthe following tasks:

[0745] 1 From the Configuration Manager, select the FFP tab

[0746] 2 Select the FFP group from the expanded tree or double-click onthe FFP in the graphic area. The Attributes tab for the group displays.

[0747] 3 Modify the required values shown in blue and red by clicking onthe value, then select the new option from the drop-down list.

[0748] 4 Click the Modify tool to download the changes to the NE. Thechanged values will be displayed in the Value column.

[0749] Deactivate an FFP Group (FLASH-192)

[0750] Active FFPs for a FLASH-192 can be deactivated, by performing thefollowing tasks:

[0751] 1 In any tab in the Configuration Manager, select the Manage FFPoption from the NE menu. The Manage FFP dialog displays.

[0752] 2 Select the shelf from the Shelf drop-down list.

[0753] 3 Select the rate from the Rate drop-down list.

[0754] 4 Select the FFP in the Existing FFP column.

[0755] 5 Select Delete from the Edit menu. The FFP will be moved fromthe Existing FFP to the Non-Existing FFP column and will be deactivated.

[0756] Managing Wavelengths

[0757] Use the NETSMART Wavelength Management feature to produce areport about wavelength inventory in your network. The report includes:

[0758] Wavelength (in nm)

[0759] Frequency (in THz)

[0760] Part number for narrowband optics or transponder card

[0761] AID

[0762] Wavelength availability and primary status

[0763] OCN WLR (Optical Carrier Level n Wavelength Received)

[0764] OCN OPR (Optical Carrier Level n Optical Power Received)

[0765] WCH OPT (Wavelength Channel Optical Power Transmitted)

[0766] WDM OPR (Wavelength Division Multiplexer Optical Power Received)

[0767] WDM OPT (Wavelength Division Multiplexer Optical PowerTransmitted)

[0768] Note: To avoid confusion, the window display is static (is notupdated) once the view is requested You must use the Reload tool or theReload NE List command to redisplay the window and view updatedinformation.

[0769] Wavelength Support

[0770] The following wavelengths are supported: Wavelength (nm)Frequency (THz) 10 G Part Number 1535.82 195.2 08 1536.60 195.1 091537.39 195 10 1538.18 194.9 11 1538.97 194.8 12 1539.76 194.7 131540.55 194.6 14 1541.34 194.5 15 1542.14 194.4 16.

[0771] Produce a Wavelength Inventory Report

[0772] The Wavelength Management window can be started from anyapplication with a NETSMART menu item. Wavelength (nm) Frequency (THz)10 G Part Number. 1542.93 194.3 17 1543.73 194.2 18 1544.52 194.1 191545.32 194 20 1546.11 193.9 21 1546.91 193.8 22 1547.71 193.7 231548.51 193.6 24 1549.31 193.5 25 1550.11 193.4 26 1550.91 193.3 271551.72 193.2 28 1552.52 193.1 29 1553.32 193 30 1554.13 192.9 311554.94 192.8 32 1555.74 192.7 33 1556.55 192.6 34 1557.36 192.5 351558.17 192.4 36 1558.98 192.3 37 1559.79 192.2 38 1560.60 192.1 39

[0773] If you open this window from the Topology window, the followingselections are available:

[0774] Select a number of NEs.

[0775] Select a number of groups.

[0776] Select a number of NEs and groups.

[0777] Select the Network group.

[0778] If any of these selections are made, the Wavelength Managementwindow displays with only the selected FLASHWAVE terminals. Otherwise,all existing FLASHWAVE terminals are displayed To produce a wavelengthinventory report, perform the following tasks:

[0779] 1 From the NETSMART menu, select Wavelength Management. TheWavelength Management window displays.

[0780] 2 The list area contains a list of all FLASHWAVE terminal NEs.Click on an NE to display its data.

[0781] 3 To filter the columns of the data display, select the Filtertool from the toolbar.

[0782] 4 Click on the first button below the Field label. A list ofvalues to filter with displays. Values include Wavelength (nm),Frequency (THz), Transponder or I0 G part #, AID, Status, OCN WLR, OCNOPR, WCH OPT, WDM OPR, and WDM OPT. Click to select one of these values.

[0783] 5 Once a filtering value has been selected, the Test buttonbecomes active. Click on the Test button to display a series of valuesto test against for filtering; one of:

[0784] contains

[0785] !contains

[0786] starts with

[0787] !starts with

[0788] ends with

[0789] ends with

[0790] 6 Click to select one of the values listed above. Boolean valuescan be used to filter by selecting one of and/or from the Logic button.

[0791] 7 Once all filtering values are selected, click Ok to redisplaythe Wavelength Management values with the filter(s) applied.

[0792] NGDLC Services

[0793] Next generation digital loop carrier (NGDLC) systems enablecarriers to provide integrated access between the customer premises andthe public network. NGDLC supports concentration of switched traffic andgrooming of non-switched traffic.

[0794] You may view and edit Next Generation Digital Loop Carrierservices including the TR-008, TR-303, or INA interface groups for aFACTR NE. Each of these groups is created by autodiscovery. Choose themode (I, II, or III), the mapping sequence (D1D or D4) and the bypasspair option (1 or 2). TR-303 defines an interface between a centraloffice switch and a remote terminal to handle all call processing andoperational functions for the DLC system. TR-303 is a versatileinterface supporting a large number of subscribers and transportbandwidth, providing carriers with the ability to choose a concentrationratio geared to traffic engineering guidelines. For TR-303 DS0s, theNETSMART user can see the assigned Call Reference Value (CRV), which isa number between 1 and 2016 that is assigned to a TR-303 DS0.

[0795] Edit a TR-008 or TR-303 Interface Group

[0796] This procedure edits TR-008 and TR-303 parameters for those NEsthat support these interfaces. It also places the interface in serviceor, for maintenance purposes, out of service. Placing an NE inmaintenance state is not service affecting. However, once an NE has beenplaced in a maintenance state, actions performed on that NE may beservice affecting (a loopback, for instance, is service affecting).

[0797] 1 Log on the NE.

[0798] 2 From the Configuration Manager, select the Interface Type tab.The Interface Type tab displays.

[0799] 3 A blue dot in the upper right-hand corner indicates that aninterface group has children. Double-click the TR-008 or TR-303 box inthe graphical area or, in the expanded tree, select the item thatcorresponds to the interface to be modified. The Attributes dialogdisplays.

[0800] 4 Click on the interface option to be changed. Only interfaceoptions displayed in blue can be changed. Select the new option from thedrop-down list

[0801] 5 Click the Modify tool or select the Update option from theOperations menu to make the changes.

[0802] 6 Click to select the tool for the correct operation: InServ,OOSMA, OOSMT. The same options can also be chosen from the Operationsmenu.

[0803] Edit an INA Interface Group

[0804] This procedure allows the user to modify INA interface attributesand put T1s in service or take them out of service for maintenance.Placing an NE in maintenance state is not service affecting. However,once an NE has been placed in a maintenance state, actions performed onthat NE may be service affecting (a loopback, for instance, is serviceaffecting).

[0805] 1 Log on the NE.

[0806] 2 From the Configuration Manager, select the Interface Type tab.

[0807] 3 A plus sign to the left of an interface group indicates thatthis interface group has children. Expand the tree list and select theTi to be modified.

[0808] 4 The Attributes dialog (FIG. 27) displays.

[0809] 5 Only interface options displayed in red or blue can be changed.Select a new option from the drop-down list that is displayed when thevalue is clicked.

[0810] 6 Click the Modify tool to complete the changes.

[0811] 7 Click to select the tool for the correct operation: InServ,OOSMA, or OOSMT. The same options can also be chosen from the Operationsmenu.

[0812] Performance Management

[0813] Performance Management is an optional feature and is startedusing a different NETSMART command than the regular startup command. Ifyou cannot access this feature, please contact your NETSMARTadministrator. For information about enabling and disabling PerformanceManagement, refer to “NETSMART Optional Features” in the NETSMARTInstallation and Administration Guide (FJTU-320-940-150).

[0814] A NETSMART user needs a way of accessing the PM Monitoringparameters on a Network Element (NE) to determine how an NE isperforming in the network. The PM feature provides the mechanism for theuser to query and set PM Monitoring parameters on one or more NE(s). Acomprehensive listing of PM parameters for each NE can be found in theappropriate NE manual. Most PM operations may be applied to one or moreNE(s), to multiple cards or facilities on a single NE, or to a singlecard or facility on a single NE. Use Performance Manager to:

[0815] Enable and disable a performance monitoring report

[0816] Retrieve performance monitor reporting status

[0817] Initialize the performance registers for an NE

[0818] Set individual threshold values

[0819] Retrieve current threshold values

[0820] Retrieve historical performance data

[0821] Operations that can be applied only to a single card or facilityon a single NE are:

[0822] Setting of individual threshold values

[0823] Retrieval of current threshold values

[0824] Retrieval of performance data

[0825] Management Procedures

[0826] This section describes the procedures for using the PerformanceManager. Performance Manager is supported for the following NEs:

[0827] FLASH-192 (02.03)

[0828] FLASH-192 (04.02)

[0829] FLASHWAVE (02.01)

[0830] FLASHWAVE (01.03)

[0831] FLM 2400 ADM (14.02S).

[0832] FLM 2400 ADM (14.02BS)

[0833] FLM 600 ADM (14.02)

[0834] You can display the Performance Manager window in three differentviews, depending on how the window is accessed. Views include: ElementView, Equipment View and Groups/Facilities View.

[0835] Element View: Accessing Performance Manager from the Topologywindow displays the Element View.

[0836] Equipment View: Accessing Performance Manager from theConfiguration Manager Equipment Tab displays the Equipment View.

[0837] Groups/Facilities View: Accessing Performance Manager from theConfiguration Manager Groups/Facilities tab displays theGroups/Facilities View.

[0838] Performance Manager Element View

[0839] To display Performance Manager in Element View, select an NE orseveral NEs in the Topology window and then select PerformanceManagement from the NETSMART menu. If no NEs are selected, a list ofavailable NEs will be displayed in the Performance Manager window afterit is launched. The view is divided into two main parts. The Selectionarea in the top portion of the view displays selected elements in theSelected Elements list. Radio buttons to the right of the Interval labelare used to define a monitoring interval. The bottom portion of the viewdisplays monitoring data.

[0840] Start and Stop Monitoring

[0841] Note: If the Performance Manager was started from a selected NEor NEs, there will be no elements in the Available Elements list and theselected NE(s) will be displayed in the Selected Elements list. If youstarted Performance Management from the NETSMART menu with no NEselected, all NEs will be displayed in the Available Elements list. Thefollowing information assumes that Performance Management was selectedfrom the Operations menu with no NE selected (all NEs will appear in theAvailable Elements list).

[0842] 1 To begin monitoring, select the Monitors tab in the PerformanceManager window. This is the default tab for the Element view.

[0843] 2 To select NEs to monitor, select an item in the AvailableElements column and use the Add button to add it to the SelectedElements column.

[0844] 3 To remove an item from the Selected Elements column, highlightthe item in the Selected Elements column and click the Remove button.After the in-progress message bar disappears, the entry is added to themonitoring data area. Verify the status of the initialization in thethird column.

[0845] 4 To add all items to the Selected Elements column, click the AddAll button.

[0846] 5 To remove all the items in the Selected Elements column, clickthe Remove All button. After the in-progress message bar disappears, theentry stays in the list, but the status is changed to Disable.

[0847] Note: When it is impossible to use a selection, that selection isgrayed-out. For example, in PM Element View (from NE): Monitors Tab theAdd and Add All buttons cannot be used because there is nothing in theAvailable Elements: list to add. The Remove button cannot be used untilan element in the Selected Elements: list is selected.

[0848] 6 Define the interval for monitoring using the Interval radiobutton. Options are 15 Min. (15-minute intervals) or 1 Day. The defaultvalue is 15 minutes. If you select 15 Min., data is retrieved from theNE 15-minute registers. If you select 1 Day, data is retrieved from theNE 1-day registers

[0849] 7 Click the Mon On tool in the toolbar or select Turn PerformanceMonitoring On from the Operations menu (FIG. 28).

[0850] 8 To stop monitoring, select the Monitors tab and then click theMon Off tool in the toolbar or select Turn Performance Monitoring Offfrom the Operations menu.

[0851] Initialize Registers

[0852] To reset all registers to zero values, you will initialize theregisters. To initialize registers:

[0853] 1 Select the Registers tab in the Element view (FIG. 29).

[0854] 2 To select NEs to initialize, select an item in the AvailableElements column and use the Add button to add it to the SelectedElements column.

[0855] 3 To remove an item from the Selected Elements column, highlightthe item in the Selected Elements column and click the Remove button.

[0856] 4 To add all items to the Selected Elements column, click the AddAll button.

[0857] 5 To remove all the items in the Selected Elements column, clickthe Remove All button.

[0858] Note: When it is impossible to use a selection, that selection isgrayed out. For example, in PM Element View from NE): Monitors Tab theAdd and Add All buttons cannot be used because there is nothing in theAvailable Elements: list to add. The Remove button cannot be used untilan element in the Selected Elements: list is selected.

[0859] 6 Select the Init tool in the toolbar or select InitializePerformance Registers from the Operations menu. Selecting this optionwill initialize all the registers in the NEs to zero (Initialized

[0860] Retrieve Performance Data

[0861] Occasionally you will want to retrieve performance data forreporting or analysis. To retrieve performance data, perform thefollowing tasks:

[0862] 1 Select the Database tab in the Element view (FIG. 30).

[0863] 2 Select the element(s) from the Available Elements list.

[0864] 3 Use the Add button to add it to the Selected Elements column.

[0865] 4 To remove an item from the Selected Elements column, highlightthe item in the Selected Elements column and click the Remove button.

[0866] 5 To add all items to the Selected Elements column, click the AddAll button.

[0867] 6 To remove all the items in the Selected Elements column, clickthe Remove All button.

[0868] Note: When it is impossible to use a selection, that selection isgrayed out. For example, in PM Element View (from NE): Monitors Tab theAdd and Add All buttons cannot be used because there is nothing in theAvailable Elements: list to add. The Remove button cannot be used untilan element in the Selected Elements: list is selected.

[0869] 7 Select or type values in the following fields:

[0870] Interval—Displays the time period interval. Possible options are15 Min. or 1 Day. The default is 15 minutes. If you select 15 Min. thecollected data will be divided into 15-minute periods. If you select 1Day, the collected data will be reported in 1-day periods.

[0871] NMS Start Date—Select the date when NETSMART started receivingdata from the NE. A default format is provided.

[0872] NMS Start Time—Select the time when NETSMART started receivingdata from the NE.

[0873] NMS End Date—Select the date when NETSMART stopped receiving datafrom the NE.

[0874] NMS End Time—Select the time when NETSMART stopped receiving datafrom the NE.

[0875] 8 Select Reload from the Operations menu or click the Reload toolfrom the toolbar to start retrieving data.

[0876] Performance Manager Equipment View

[0877] To display the Performance Manager Equipment view, select a cardin the Configuration Manager Equipment tab and then click on theRetrieve tool in the toolbar. Otherwise, right-click to display a pop-upmenu and then select Display PM from the pop-up menu. If a card does nothave PM registers, the PM tool will not be displayed in the toolbar FIG.31 shows the Performance Manager Equipment view. The Equipment viewdisplays only the Registers tab and facilitates setting registerthresholds and retrieving current performance registers. Fields in thedisplay include:

[0878] NMS Time—NETSMART time.

[0879] NE Time—The time on the NE.

[0880] AID Type—Type of Access Identifier.

[0881] AIM—Access Identifier name.

[0882] Register—Register name.

[0883] Val ue—Value of the register that was retrieved.

[0884] Range—Allowable range for the register Value.

[0885] Threshold—Indicator to the NE to regenerate the threshold reportif the threshold was exceeded.

[0886] Default Threshold—When an NE is first started, this is thedefault value set by the NE. This value can be reset using the proceduredescribed in “Set Threshold”.

[0887] Validity—This value is valid only for FLASH-192 and FLASHWAVENEs. Under normal operating conditions, this value should be FALSE. PMregisters are accumulated in 15-minute intervals; if any data beingreported is not for the full 15-minute interval this value will bereported as TRUE.

[0888] Location—This value indicates where the data is coming from(near-end or far-end). Equipment registers will always be far-end.

[0889] Direction—For equipment, this will always report N/A as thephysical characteristics of equipment have no direction. Typically thevalue reported for facilities will be Tx or Rx.

[0890] Time Interval—This value is always N/A for equipment. Forfacilities the time reporting interval will be displayed as either 15MIN or 1 DAY.

[0891] Index—This value will always be 0 for equipment. For facilities,the current register (0) plus previous registers 1 to 32 will bedisplayed. The Monitors and Database tabs cannot be selected, becauseequipment registers are not counters; they are current operating levelsfor items such as Laser Bias Current Normalized (LBCN). Because of this,monitoring cannot be turned on or off and the database will not containany historical data.

[0892] Set Threshold

[0893] Performance monitoring registers can, potentially, be collectedfor thousands of circuits, creating an overwhelming amount of data. Tolimit this data, thresholds for data collection can be set. If thesethresholds are not crossed, the assumption is that the NE performance isacceptable. A default threshold value exists for each register. Thethreshold for any register can be set and changed. To set thresholds:

[0894] 1 Select equipment from the Available Equipment list and clickthe Add button to add the equipment to the Selected Equipment list

[0895] 2 Select a numbered row in the report and then click the Set toolin the toolbar. The Set Thresholds dialog displays.

[0896] 3 Type a new value for the threshold. Threshold ranges areNE-dependent and are displayed when you select the row that you will setregisters for. You can also refer to the System Engineering section ofthe Fujitsu Network Communications web site for the TL1 threshold valuespecification for each NE.

[0897] 4 Click OK to select the threshold and close the dialog.

[0898] Retrieve New Data

[0899] To retrieve new performance data:

[0900] 1 Select equipment from the Available Equipment list and clickthe Add button to add them to the Selected Equipment list.

[0901] 2 Select the Reload tool from the toolbar. The Reload toolupdates the report for the equipment contained in the Selected Equipmentlist and for the values specified in the Location, Direction, TimeInterval, and Index fields.

[0902] Performance Manager Groups/Facilities View

[0903] To display Performance Manager in the Groups/Facilities View,select a facility in the Configuration Manager Groups/Facilities tab andthen click on the Retrieve tool in the toolbar. Otherwise, right-clickto display the pop-up menu and then select Display Performance from thatpop-up menu. The Monitor tab is the default initial display.

[0904] If a facility has PM registers, when that facility is selected,the PM tool will become active in the toolbar. FIG. 32 shows thePerformance Manager window in the Groups/Facilities view. TheGroups/Facilities view contains the Monitors, Registers, and Databasetabs and allows you to turn reporting on or off, to retrieve current PMregisters from the facility and to retrieve historical data from thedatabase. The Monitors tab is grayed-out on any group/facility that doesnot support performance monitoring. By default, the facility selected inConfiguration Manager is the one displayed in Performance Manager andthe Interval option is set to 15 Min. (the default). Fields in thedisplay include:

[0905] NMS Time—NETSMART time.

[0906] NE Time—The time on the NE.

[0907] AID Type—Type of Access Identifier.

[0908] AID—Access Identifier name.

[0909] Register—Register name.

[0910] Value—Value of the register that was retrieved.

[0911] Range—Allowable range for the register Value.

[0912] Threshold—Indicator to the NE to regenerate the threshold reportif the threshold was exceeded.

[0913] Default Threshold—When an NE is first started, this is thedefault value set by the NE. This value can be reset using the proceduredescribed in “Set Threshold”.

[0914] Validity—This value is valid only for FLASH-192 and FLASHWAVENEs. Under normal operating conditions, this value should be FALSE. PMregisters are accumulated in 15-minute intervals; if any data beingreported is not for the full 15-minute interval this value will bereported as TRUE.

[0915] Location—This value indicates where the data is coming from(near-end NEND or far-end FEND).

[0916] Direction—Typically the value reported for facilities will be Txor Rx.

[0917] Time Interval—For facilities the time reporting interval will bedisplayed as either 15 MIN or 1 DAY.

[0918] Index—For facilities, the current register (0) plus previousregisters 1 to 32 will be displayed

[0919] Start and Stop Monitoring

[0920] 1 To start monitoring, select the Monitors tab in the PerformanceManager Groups/Facilities view. The reporting status is automaticallyretrieved and displayed.

[0921] 2 To select NEs for monitoring, select an item in the AvailableFacilities list and use the Add button to add it to the SelectedFacilities list. By default, the facility that is selected whenPerformance Manager is launched is already in the Selected Facilitieslist.

[0922] 3 To remove an item from the Selected Facilities column,highlight it in the Selected Facilities column and click the Removebutton.

[0923] 4 To add all the items to the Selected Facilities column, clickthe Add All button.

[0924] 5 To remove all the items in the Selected Facilities column,click the Remove All button.

[0925] 6 Choose the location by selecting one of the Location radiobuttons. Possible choices are NEND (near-end) or FEND (far-end).

[0926] 7 Choose the direction by selecting one of the Direction radiobuttons. Possible choices are Receive, Transmit or NA (Not Applicable).This list is dynamically updated based on the selected facility.

[0927] 8 Select the interval for monitoring using the Interval: radiobutton. Options are 15 Min. or 1 Day. The default is 15 minutes. If youselect 15 Min., data is retrieved from the NE 15-minute registers. Ifyou select 1 Day, data is retrieved from the NE 1-day registers.

[0928] 9 In the Start Index and End Index fields, select a value between0 and 32 for registers. 0 is the current register and there may be up to32 previous registers. The End Index value must always be higher thanthe Start Index value.

[0929] 10 Click the Mon On tool in the toolbar to start monitoring.

[0930] 11 To stop monitoring, select the Monitors tab and then click theMon Off tool in the toolbar

[0931] Initialize Performance Registers

[0932] To initialize performance registers:

[0933] 1 Select the Registers tab in the Groups/Facilities view.

[0934] 2 Select the Init tool in the toolbar. Selecting this option willinitialize all the selected NE facility registers to zero.

[0935] Retrieve Register Data

[0936] To retrieve register data, select the Registers tab in the PMGroups/Facilities view. Once this tab is selected, a command is sent tothe NE to retrieve register data for the selected facility. This data isdisplayed using the default parameters for Location, Direction, Intervaland Start and Stop Indexes.

[0937] Reload Register Data in the Report

[0938] To reload new register data while in the Registers tab:

[0939] 1 Select the facilities from the Available Facilities list andclick the Add button to add them to the Selected Facilities list.

[0940] 2 Choose the location by selecting one of the Location radiobuttons. Possible choices are NEND (near-end) or FEND (far-end).

[0941] 3 Choose the direction by selecting one of the Direction radiobuttons. Possible choices are Receive, Transmit or NA (Not Applicable).This list is dynamically updated based on the selected facility.

[0942] 4 Select the interval for monitoring using the Interval radiobutton. Options are 15 Min. or 1 Day. The default is 15 Min. If youselect 15 Min., data is retrieved from the NE 15-minute registers. Ifyou select 1 Day, data is retrieved from the NE 1-day registers.

[0943] 5 In the Start Index and End Index fields of the Registers tab,select a value between 0 and 32 for registers. 0 is the current registerand there may be up to 32 previous registers. The End Index value mustalways be higher than the Start Index value. These choices may bedynamically updated, depending on the selected type of facility.

[0944] 6 Select the Reload tool in the toolbar. Selecting this tool willreload the register data for the selected facility for the indexselected in Step 2 and will display the results in the window.

[0945] Set Threshold

[0946] You can set and change the current threshold for any register. Toset thresholds, from the Performance Manager:

[0947] 1 Select the Registers tab in the Groups/Facilities view.

[0948] 2 Select facilities from the Available Facilities list and usethe Add button to add them to the Selected Facilities list.

[0949] 3 Select a numbered row in the report and then click the Set toolin the toolbar. After the Set Thresholds dialog displays, type a newvalue for the threshold.

[0950] 4 Click Ok to save the changes and close the dialog.

[0951] Retrieve Historical Data

[0952] To retrieve historical data for the selected facility in theFacility View:

[0953] 1 Select the Database tab in the Groups/Facilities view.

[0954] 2 Select elements from the Available Elements list and click theAdd button to add them to the Selected Elements list. Select Add All toadd all elements.

[0955] 3 Select the interval for monitoring using the Interval radiobutton. Options are 15 Min. or 1 Day. The default is 15 minutes. If youselect 15 Min., data is retrieved from the NE 15-minute registers. Ifyou select 1 Day, data is retrieved from the NE 1-day registers.

[0956] 4 Type values in the following fields:

[0957] NMS Start Date—Select the date when NETSMART started receivingdata from the NE.

[0958] NMS Start Time—Select the time when NETSMART started receivingdata from the NE.

[0959] NMS End Date—Select the date when NETSMART stopped receiving datafrom the NE.

[0960] NMS End Time—Select the time when NETSMART stopped receiving datafrom the NE.

[0961] 5 Click the Reload tool from the toolbar to begin retrievingdata; The resulting report is updated for the elements in the SelectedElements list and for the specified Interval, NMS Start Date, NMS StartTime, NMS End Date, and NMS End Time.

[0962] TL1 Command and Batch Processing

[0963] This section provides the procedures for entering and executingboth batch and online TL1 commands. Batch TL1 commands can be saved as afile and executed at a later time.

[0964] To start the TL-1 Editor, from the Configuration Manager NETSMARTmenu, select TL1 Editor. The Raw TL-1/TL-1 Batch window displays. Thereare three main display areas on this window.

[0965] The upper part will contain any commands that were typed in theTL1 Command text entry area

[0966] The middle part will contain any results/responses generated bythis command.

[0967] The lower part contains the TL1 Command text entry area, theActive Sessions list area and the list of saved batch files. Thisprocedure refers to the upper portion of this window as the history areaand the middle portion is referred to as the results/responses area. Thelower portion of the window is referred to as the batch listing area.

[0968] Enter Single TL1 Commands

[0969] Use the Raw TL-1/TL-1 Batch window to enter and executeindividual TL1 commands. Using individual TL1 commands is the simplestway to interact with a single NE and will ensure that the commandexecutes properly before using it in a batch file (especially one thatwill be executed on multiple NEs). When executing time-consuming TL1commands, it is best to use a TL1 batch (when individual TL1 commandsare sent for execution, the TL1 Editor remains busy waiting for commandresponse).

[0970] 1 In the Raw TL-1/TL-1 Batch Window, type in the TL1 command inthe TL1 Command field.

[0971] 2 Press the ENTER key to execute the command. The commanddisplays in the history area of the TL1 window. The command and theresults display in the results/responses area of the TL1 window. EachTL1 session corresponds to a user ID that is logged on a specific NE.Multiple sessions can exist. An active session must exist to send acommand. If no sessions exist, one can be created by issuing theACT-USER TL1 command.

[0972] Enter TL1 Commands in Batch Mode

[0973] TL1 commands can be entered into a batch file for immediateexecution or can be saved in a batch file for a scheduled execution.Before a batch can execute, at least one TID must be selected. Inaddition, the batch must have the UID and Password properties set beforethe batch can execute.

[0974] Batch commands can be exported as a file, in which case the TIDand Properties values will not be retained. Importing a TL1 file intothe TL-1 Batch Editor will override any existing commands in the editor.The command syntax for TL1 commands is described in Bellcore documentGR-831-CORE Issue 1 (November 1996).

[0975] 1 In the Raw TL-1/TL-1 Batch window, select New from the Batchmenu to display the NETSMART TL-1 Batch Editor window, where you cancreate a new batch. To edit an existing batch, double-click on anexisting batch in the batch listings at the bottom of the window orclick on a batch name and select Edit from the Batch menu. The NETSMARTTL-1 Batch Editor window displays (FIG. 4-144).

[0976] 2 Select TIDs from the Batch menu. The TID List dialog displays.

[0977] 3 Select the TID(s) for the batch by clicking to highlight theTID to which the TL1 commands will be sent. Multiple TIDs can beselected. Click a second time on the TID to deselect any unwantedvalues.

[0978] 4 If the TID that is needed is not in this list, type the name ofthe TID in the list to the left of the Add TID to List button.

[0979] 5 Click the Add TID to List button to add the TID to the list. Ifthere are no TIDs to add, this button is grayed out and unavailable.

[0980] 6 Click Ok to select the TID(s).

[0981] 7 Use the Import Batch tool to display the Import Batch dialogwhere the file to be imported can be identified, or use the Export Batchtool to display the Import Batch dialog where the location and file namefor data to be exported can be identified.

[0982] 8 Click to select the file to be imported or exported. Only onefile at a time can be selected.

[0983] 9 Click OK to select the file and close the dialog.

[0984] 10 Click the mouse to place the cursor in the free-form area ofthe NETSMART TL-1 Batch Editor (the main part of the window) and typeTL1 commands in this area.

[0985] 11 To set the properties for the batch, click on the Props toolor select Properties from the Batch menu. The Batch Properties dialogdisplays. Values must be entered in the UID and Password fields for thebatch to execute.

[0986] 12 Select or type values in the following fields:

[0987] Name:—If this is a new batch, this field is blank. If this is anexisting batch, this field displays the name of the batch. Data cannotbe entered in this field.

[0988] Owner—Displays the user name that logged on NETSMART. Data cannotbe entered in this field.

[0989] Privilege:—Select PRIVATE if only the person who created thebatch file can execute it or PUBLIC if any user with TL1 privileges canexecute the batch file.

[0990] Send Mode:—Select SERIAL if the TL1 batch of commands is to besent to one NE at a time or PARALLEL if the batch file is to be sent toall NEs in the TID list at the same time.

[0991] UID:—Type the user ID that will be used to create a new sessionfor batch execution. This user ID must be valid for each TID that wasselected using the TID List dialog. If a command within the batch filespecifies another user ID, the user ID within the batch file willoverride this user ID.

[0992] Password:—Enter the password for the User ID that was typed inthe UID field.

[0993] 13 Click Ok to save the property settings or Cancel to close thedialog without making changes.

[0994] 14 To save the batch file, click the Save As tool or select SaveAs from the File menu.

[0995] The Save As Dialog

[0996] Use the Save As . . . dialog to save a file with the existingname (overwrites the existing file) or to type a new filename and savethe file with the new name.

[0997] 1 When the Save As . . . dialog displays, type a value in theBatch name field. The file will be saved using this name.

[0998] 2 In the Raw TL-1/TL-1 Batch window, double-click to select asaved batch file from the listing area (the lowest portion of the TL1window). If there is more than one session active, select the activesession TID from the Active Sessions list. Click the Send tool or selectSend from the Batch menu to transmit the TL1 commands.

[0999] Edit TL1 Batch Commands

[1000] The TL1 batch file can be edited and saved in the original fileor in a new batch file for a scheduled execution. The new batch musthave the UID and Password properties set before the batch can execute.Batch commands can be exported as a file, in which case the TID andProperties values will not be retained. Importing a TL1 file into theBatch Editor will override any existing commands in the editor. Thecommand syntax for TL1 commands is described in Bellcore documentGR-831-CORE Issue 1 (November 1996), which is hereby incorporated byreference.

[1001] 1 In the Raw TL-1/TL-1 Batch window, either double-click on anexisting batch in the batch listings at the bottom of the window orclick on a batch name and select Edit from the Batch menu. The NETSMARTTL-1 Batch Editor window displays.

[1002] 2 To add or change TIDs, select TIDs from the Batch menu. The TIDList dialog displays.

[1003] 3 Select the TID(s) for the batch by clicking to highlight theTID to which the TL1 commands will be sent. Multiple TIDs can beselected. Click a second time on the TID to deselect any unwantedvalues.

[1004] 4 If the TID that is needed is not in this list, type the name ofthe TID in the list to the left of the Add TID to List button. Click theAdd TID to List button to add the TID to the list. If there are no TIDsto add, this button is grayed out and unavailable.

[1005] 5 Click Ok to select the TID(s).

[1006] 6 Use the Import Batch tool to display the Import Batch dialogwhere the file to be imported can be identified, or use the Export Batchtool to display the Import Batch dialog where the location and file namefor data to be exported can be identified.

[1007] 7 Click to select the file to be imported or exported. Only onefile at a time can be selected.

[1008] 8 Click OK to select the file and close the dialog.

[1009] 9 Click the mouse to place the cursor in the free-form area ofthe NETSMART TL-1 Batch Editor (the main part of the window) and typeTL1 commands in this area.

[1010] 10 To modify the properties for the batch, click on the Propstool or select Properties from the Batch menu. The Batch Propertiesdialog displays. Values in the UID and Password fields must be changedso that the batch can execute.

[1011] 11 Select or type to change values in the following fields:

[1012] Name:—If this is a new batch, this field is blank. If this is anexisting batch, this field displays the name of the batch. Data cannotbe entered in this field.

[1013] Owner—Displays the user name that logged on to NETSMART. Datacannot be entered in this field.

[1014] Privilege:—Select PRIVATE if only the person who created thebatch file can execute it or PUBLIC if any user with TL1 privileges canexecute the batch file.

[1015] Send Mode:—Select SERIAL if the TL1 batch of commands is to besent to one NE at a time or PARALLEL if the batch file is to be sent toall NEs in the TID list at the same time.

[1016] UID:—Type the user ID that will be used to create a new sessionfor batch execution. This user ID must be valid for each TID that wasselected using the TID List dialog. If a command within the batch filespecifies another user ID, the user ID within the batch file willoverride this user ID.

[1017] Password:—Enter the password for the User ID that was typed inthe UID field.

[1018] 12 Click Ok to save the property settings or Cancel to close thedialog without making changes.

[1019] 13 To save the batch file, click the Save As tool or select SaveAs from the File menu.

[1020] 14 When the Save As . . . dialog displays, type a value in theBatch name field or leave the old name if you do not want to change it.The file will be saved using this name.

[1021] 15 In the Raw TL-1/TL-1 Batch window, double-click to select asaved batch file from the listing area (the lowest portion of the TL1window). If there is more than one session active, select the activesession TID from the Active Sessions list. Click on the Send tool orselect Send from the Batch menu to transmit the TL1 commands.

[1022] Using the TL1 Console

[1023] This section provides the procedures for using the TL1 Console.The TL1 Console window allows a user to view the TL1 activity generateddue to a user's actions; for example, log on to NE, create crossconnect,etc. System-level TL1 activities include all the TL1 activities that aresent to or received from the NEs being managed, such as TL1 command andresponse, autonomous messages (REPT-*), raw TL1 command and response,and RTRV-HDR.

[1024] By default, all security roles defined in NETSMART have theTL1Console user function, which allows users to view the TL1 activitiesthat they generated. The NetSmartUserAdmin role has the TL1SuperConsolefunction, which allows users to view the system TL1 activities. If therole includes the TL1SuperConsole user function, the user with this rolecan use the TL1 Console window to view system-level TL1 activities. As aTL1SuperConsole user, up to five TL1 Console windows can be started. Bydefault, the TL1 messages viewed by the TL1Console user include thecommand and response received from the NE. For information about viewingother TL1 record attributes or changing the order of the displayedattributes, refer to Section A.13.1, TL1 Console Rearrange AttributesDialog. As a TL1Console user, you can start only one TL1 Console window.

[1025] For information about modifying the security roles, refer toRoles Tab. To start the TL1 Console, from the NETSMART menu, select TL1Console. The TL1 Console window displays. As soon as you open the TL1Console, the display of TL1 events begins and scrolls automatically todisplay additional events. The TL1 Console window displays a maximum of1000 records at a time.

[1026] Display TL1 Messages

[1027] The display can be started, stopped or paused by selecting Start,Stop or Pause from the Operations menu or by selecting one of the Start,Stop, or Pause tools from the toolbar.

[1028] 1 The TL1 console starts with the default setting, which displaysTL1 messages. The server will start sending messages to the console. Toadd, remove, or rearrange the attributes to be displayed, use theRearrange Attributes dialog. For more information, refer to RearrangeTL1 Attributes. If the display was paused earlier by selecting the Pausebutton, the console will display the messages that were sent during thepause and will then start to display new messages. If the display wasstopped earlier by selecting the Stop button, the new real-time messageswill begin to display. The Start button becomes active only when thedisplay has been paused or stopped.

[1029] 2 To pause the message display, select Pause from the Operationsmenu or click the Pause tool. This option pauses the display of TL1events to the console. Internally, the messages are buffered for up to1000 records; these records will be displayed when you select Start torestart the display.

[1030] 3 To stop display of any messages in the console, select Stopfrom the Operations menu or select the Stop tool in the toolbar. Theserver stops sending messages to the console.

[1031] Rearrange TL1 Attributes

[1032] Adding, removing, or rearranging the attributes to be displayedin TL1 Console is accomplished by using the Rearrange Attributes dialog.

[1033] 1 To open this dialog, select Rearrange Log Attributes from theView menu or click the Rearran . . . tool in the toolbar. The RearrangeAttributes dialog displays.

[1034] 2 To add an attribute to the Selected List, highlight theattribute in the selections beneath the Attribute List and then clickthe Add button.

[1035] 3 To remove an attribute from the Selected List, highlight theattribute in the Selected List and then click the Remove button.

[1036] 4 To add or remove all attributes, use the AddAll button or theRemoveAll button. TL1Msg is the default item in the Selected List andcannot be removed.

[1037] 5 To change the order of the attributes in the list, select anattribute and then click the Up button to move the attribute up in thelist or the Down button to move the attribute down in the list.

[1038] 6 Click OK to save the settings and close this dialog or clickCancel to cancel all changes and close this dialog.

[1039] Filter TL1 Messages

[1040] Messages to be displayed in the TL1 Console can be filtered usingthe Filter TL1 Messages dialog.

[1041] 1 To open the Filter TL1 Messages dialog, select Filter from theOperations menu in the TL1 Console window or click the Filter tool inthe toolbar. The following dialog displays.

[1042] 2 Messages can be filtered based on the NE TID or the messagetype. Select the filter from the NE ID drop-down list. To filter the TL1message display based on the NE TID, select:

[1043] Starts with—If you want the NE to start with the specified value.

[1044] Ends With—If you want the NE to end with the specified value.

[1045] Contains—If you want the NE to contain the specified value. Typethe text relevant to your NE ID selection in the Value field (forexample, FLM) and check the Case Sensitive box to search for the NEusing the case-sensitivity specified for the typed value.

[1046] 3 To filter messages based on the message type, in the MessageType screen area, select the message type(s) that you want to bedisplayed in the TL1 Console window. The TL1SuperConsole user can filterall message types. The TL1Console user can only view and filter thefollowing messages: Command, Response and Acknowledgement. The completelist of message types includes: Unparsed, Send Raw, Autonomous, ReceivedRaw, Command, Acknowledgement, and Response.

[1047] 4 Click OK to make the changes and close the dialog or clickCancel to close the dialog without making any changes.

[1048] Reports

[1049] This section provides the procedures for reporting informationfrom the NETSMART databases. All the reports are similar infunctionality and access methods.

[1050] Link Report

[1051] Use the Link Report window to view and edit physical linkinformation in the NETSMART database. Read-only (view) functions includefiltering and sorting of displayed physical links. Edit functionsinclude modification of physical link names and deletion of physicallinks from the system. The Link Report can be displayed as either:

[1052] A global view (all physical links in the system)

[1053] A group link view (all physical links belonging to a particularlink that is displayed on the Topology map window)

[1054] NETSMART Crossconnect Report

[1055] The crossconnect Report dialog displays a report containinginformation about a selected type of crossconnect.

[1056] 1 In one of the Crossconnect tabs, select Report from theOperations menu or select the Report tool from the toolbar. In thecascade to the right of the Report menu label, select the type ofcrossconnect to report. The Crossconnect Report dialog (FIG. 33)displays.

[1057] 2 Use the tools on the toolbar or select Operations menu items toperform the following functions.

[1058] Select the Print tool to display the Print dialog to print areport.

[1059] Select the Filter tool to display the Filter dialog to filter theinformation displayed.

[1060] Select the Sort tool to display the Sort dialog to sort theinformation displayed.

[1061] Select the Columns tool to display the Column Settings dialog todetermine the columns to be displayed.

[1062] Select the Deselect tool to remove the selection shading from anyselected screen area(s). The tool will be grayed out and unavailable ifno selection has been made.

[1063] Select the Reload tool to reload information from the NETSMARTdatabase.

[1064] 3 Once you have completed operations in this dialog, click Closeto close the report.

[1065] NETSMART Crossconnect Trail Report

[1066] The Crossconnect Trail window displays a report containinginformation about all the crossconnects in all the NEs that areautodiscovered in the Topology window.

[1067] 1 Access this dialog by selecting Query NE from the Topology viewEdit Menu.

[1068] 2 In the dialog, select Crossconnect Name from the choice boxlabeled Query by and type the Crossconnect name or another valid valuein the adjoining text field. Wild card searches are allowed, so theentry can either be a name or part of a name followed by a % sign. A %sign can be entered alone, in which case all the crossconnects will beretrieved from the database. The text field cannot be left blank.Apostrophes cannot be used. The apostrophe interferes with Oraclesemantics. For either of the two cases, a popup dialog prompts you toenter a name or to refrain from using an apostrophe in the search name.

[1069] 3 Click Ok to produce the report or click Cancel to cancel andclose this dialog.

[1070] 4 The NETSMART Crossconnect Report window displays.

[1071] 5 Use the tools on the toolbar or select Operations menu items toperform the following functions.

[1072] Select the Print tool or select Print from the Operations menu todisplay the Print dialog to print a report.

[1073] Select the Filter tool or select Filter from the Operations menuto display the Filter dialog to filter the information displayed.

[1074] Select the Sort tool or select Sort from the Operations menu todisplay the Sort dialog to sort the information displayed.

[1075] Select the Columns tool or select Column Settings . . . from theOperations menu to display the Column Settings dialog to determine thecolumns to be displayed.

[1076] In a multipage report, use the Previous and Next tools to go tothe previous and next page of the report.

[1077] Use the DelXC tool to delete a crossconnect.

[1078] Select the Deselect tool or select Deselect from the Operationsmenu to remove the selection shading from any selected screen area(s).The tool and the menu selection will be grayed out and unavailable if noselection has been made.

[1079] Select the Reload tool to reload information from the NETSMARTdatabase.

[1080] 6 When completing operations in this window, select Close fromthe File menu to close the report.

[1081] Delete a Crossconnect from the Trail Report

[1082] A crossconnect can be deleted from the NETSMART CrossconnectTrail Report. In the NETSMART Crossconnect Trail Report, each of therows represents one crossconnect record. Crossconnects can be deletedfrom the NETSMART Crossconnect Trail Report by selecting the appropriaterow(s).

[1083] 1 After the NETSMART Crossconnect Trail Report displays, selectthe row(s) to delete using the mouse. For multiple selections, you havetwo options:

[1084] Hold down the SHIFT key and click on the desired rows to select acontiguous set of records.

[1085] Hold down the CTRL key and click on the desired rows to select anon contiguous set of records.

[1086] 2 Either select the tool labeled DelXC from the toolbar, or fromthe Operations menu select Crossconnect. From the Crossconnect runoffmenu, select Delete XC.

[1087] 3 Once the row(s) have been selected from the table in the reportpanel, select either the tool labeled DelXC, or from the Operations menuselect Crossconnect and from the runoff menu select Delete XC. Some ofthe crossconnects may be redlined. If so, when the Ok button is clickedon the Confirmation dialog, an Information Message box indicates thatsome of the crossconnects selected could be set to redline, and askswhether you would like to delete the Crossconnects not redlined and skipthe redlined ones. If the Y (Yes) option is selected, the unredlinedcrossconnects are deleted. If N (No) is selected, control is returned tothe table in the Report from where the selections were made. If Yes wasselected, the report will redisplay without the deleted crossconnect. IfY (Yes) is selected, the crossconnects should be deleted. However, therecould be reasons for which the delete operation for a few crossconnectsmight fail. In that case a dialog provides a list of failed crossconnectdeletes and the reason why that delete from the report failed.

[1088] 4 To verify that the changes have been made, select Report fromthe Operations menu, then select the appropriate type of crossconnect. Areport is displayed showing all the selected types of crossconnects.

[1089] Printing

[1090] This section describes the procedures associated with printingNETSMART information. This information includes:

[1091] Printing a report

[1092] Saving a report to a disk

[1093] Printing a graphical view

[1094] Selecting a table area for printing

[1095] Previewing print output

[1096] Setting up a page for printing

[1097] Printing Overview

[1098] Use the NETSMART Print dialog to enter print commands and toprint reports to a file or to a printer. The following describes pagelayout and wrapping:

[1099] By default, if a row is wider than a page, the data is wrappedinside the cell.

[1100] Table rows are wrapped into multiple table regions, but only onetable region is printed on each page, regardless of how many tableregions can fit into one page. Table rows that extend beyond a singlepage are broken into side-by-side pages on cell boundaries

[1101] A Fit Page Width button is provided in the Page Setup dialog.When this button is selected, regardless of how wide a table row is, thetable width is set to the same as the page width.

[1102] Note: A maximum of 100 lines of output is produced for eachreport.

[1103] Print a Report

[1104] 1 After displaying a tabular report, print the data by selectingeither the Print option on the File menu or by selecting the Print toolfrom the toolbar. The Print option on the File menu is not alwaysavailable. The NETSMART Print dialog displays.

[1105] 2 Select or type values in the following fields:

[1106] Print To—Select the output format: Printer, Text File, orPostScript File.

[1107] Printer Command:—For text/postscript file output, this field willbe grayed-out and unavailable. For printed output, type any validprinter command(s) in this field.

[1108] File Name:—If you are printing to a file, use this field to typea file name.

[1109] Orientation—For printer output, select whether the printed outputshould be in landscape or portrait format.

[1110] Paper Size—For printer output, select the size of paper for theprinted report.

[1111] 3 Use the Preview . . . button to display a print preview.

[1112] 4 Use the Setup . . . button to set up printing parameters.

[1113] 5 Click Ok to send the data to the specified output device.

[1114] 6 Click Apply to apply the changes and leave the dialog open.

[1115] 7 Click Cancel to close the dialog without sending the data tothe output device.

[1116] Save a Report to a Disk

[1117] Certain tabular style reports can be saved to a disk in text file(.txt) or PostScript (.ps) format.

[1118] 1 After displaying a tabular report, click the Print tool orselect the Print Table option from the File menu. The NETSMART Printdialog displays.

[1119] 2 Select or type values in the following fields:

[1120] Print To—Select one of Text Fi le or PostScript File.

[1121] Printer Command:—For text/postscript file output, this field willbe grayed-out and unavailable.

[1122] File Name:—Type the name of the file to be created. Click on thebutton to the right of this field to display the File Selection dialogwhere you can select a location for the file.

[1123] Orientation—This field is grayed out and not available fortext/postscript file output.

[1124] Paper Size—This field is grayed out and not available fortext/postscript file output.

[1125] 3 Use the Preview . . . button to display a print preview.

[1126] 4 Use the Setup . . . button to set up printing parameters.

[1127] 5 Click Ok to save the data to the specified location.

[1128] 6 Click Apply to apply the changes and leave the dialog open.

[1129] 7 Click Cancel to close the dialog without saving any data.

[1130] Print a Graphical View

[1131] The Print View option on the File menu lets you print what yousee on the screen. This option is available in components that havegraphic images (such as Topology). It is also enabled in some componentsthat produce reports. If this selection is not available, it isgrayed-out.

[1132] 1 After displaying a graphical view, print the view by selectingthe Print View option on the File menu. The NETSMART Print dialog

[1133] 2 Select or type values in the following fields:

[1134] Print To—Select the output format: Printer, Text File orPostScript File.

[1135] Printer Command:—For text/postscript file output, this field willbe grayed-out and unavailable. For printed output, type any validprinter command(s) in this field.

[1136] File Name:—If you are printing to a file, use this field to typea file name.

[1137] Orientation—For printer output, select whether the printed outputshould be in landscape or portrait format.

[1138] Paper Size—For printer output, select the size of paper for theprinted report.

[1139] 3 Use the Preview . . . button to display a print preview.

[1140] 4 Use the Setup . . . button to set up printing parameters.

[1141] 5 Click Ok to send the data to the specified output device.

[1142] 6 Click Apply to apply the changes and leave the dialog open.

[1143] 7 Click Cancel to close the dialog without sending the data tothe output device.

[1144] Print Area

[1145] Use the Print Area option on the File menu to select an area of atable for printing. Both Set Print Area and Clear Print Area options maybe available. The Print Area option is only available for tables.

[1146] 1 Display the table that you want to print. Select Print Areafrom the File menu, and select Set Print Area from the Print Area menu.

[1147] 2 Select a row or rows for printing. For multiple printelections, you have two options:

[1148] Hold down the SHIFT key and click on the desired rows to select acontiguous set of records.

[1149] Hold down the CTRL key and click on the desired rows to select anon-contiguous set of records. When you select an area for printing, novisual changes occur.

[1150] 3 Click on the File menu, then select the Print menu item.

[1151] 4 Process printing as normal. When printing, only the selectedregion is taken into account. For example, the Print Preview option willshow only the selected region. The Clear Print Area option will clearthe selected area.

[1152] Print Preview

[1153] Use the Print Preview option on the File menu to view what willbe sent to the printer or file. The Print Preview option is availablefor any tabular data displayed on the screen.

[1154] Note: A maximum of 100 lines of tabular output is produced foreach report.

[1155] 1 After displaying a report with the appropriate data, select thePrint Preview option from the File menu. The NETSMART Print Previewdialog displays.

[1156] 2 Select the Print button to display the Print dialog.

[1157] 3 Click the Close button to close the Print Preview dialog.

[1158] NETSMART Page Setup

[1159] Each Print dialog in NETSMART contains a Setup . . . button.Selecting this button displays a dialog where you can select parametersthat affect printed output.

[1160] 1 After displaying a report with the appropriate data, select thePrint tool from the toolbar or click on one of the print options on theFile menu. The NETSMART Print dialog displays.

[1161] 2 Click to select the Setup . . . button. The NETSMART Page Setupdialog displays.

[1162] 3 In the Font area in this dialog, click in the selection list tothe right of the Name label and select the font name to be used forprinting. In the selection list to the right of the Style label, selectthe font style to be used for printing. In the selection list to theright of the Size label, select the font size to be used for printing.

[1163] 4 In the Title field, either select the default window title ortype a new value that will be the title for the print output.

[1164] 5 In the Header field, type a value that will be used as theheader information for the print output.

[1165] 6 In the Footer field, type a value that will be used as thefooter information for the print output.

[1166] 7 Check the Fit Page Width box to fit the print output within thepage width.

[1167] 8 Click Ok to send the output to the selected printer.

[1168] 9 Click Apply to make the changes but keep this dialog open.

[1169] 10 Click Cancel to close the dialog without printing.

[1170] Filtering Tabular Information

[1171] Use the Filter tool and/or select Filter from the Operations menuto refine the data that you want to see in a report or other tabularinformation. Many of the reports in NETSMART provide this optionincluding the Log Manager and Fault Manager reports.

[1172] 1 After displaying a report with the appropriate data, select theFilter tool from the toolbar or, if it is available, select the Filteroption from the Operations menu. The Filter dialog displays.

[1173] 2 Click on a button beneath the Field label to display adrop-down list to select a field.

[1174] 3 Select a field to be filtered. The Test button becomes active.Click on this button to display a series of values to test against forfiltering, one of:

[1175] contains

[1176] !contains

[1177] starts with

[1178] !starts with

[1179] ends with

[1180] !ends with

[1181] Click to select one of these values.

[1182] 4 Use Boolean values to filter by selecting one of AND/OR fromthe choice boxes beneath the Logic button.

[1183] 5 Once all filtering values are selected, click Ok to redisplaythe information with the filter(s) applied.

[1184] Sorting Information

[1185] Use the Sort dialog to specify sorting criteria in most tabularviews.

[1186] Note: There are two types of Sort dialogs. One type allows you tosort using a single argument, while another type (the Fault Manager, forinstance) allows selection of multiple sort arguments. In the secondtype (multiple arguments), it may sometimes appear that the data is notordered correctly.

[1187] 1 Click on the Sort tool or select Sort from the Operations menu.The Sort dialog displays.

[1188] 2 The sort will consider case on string sorts. To turn offcase-sensitivity, select the Ignore Case? (valid only for strings) boxat the top of the dialog.

[1189] 3 Select the sort parameters. The order in which you select theSort By buttons will determine the sort order.

[1190] 4 Use the Order button to indicate the sort order for the Sort Byparameters. Select one of Ascending (lowest to highest) or Descending(highest to lowest).

[1191] 5 Click Ok to begin the sort. The data will redisplay in the sortorder that you specified.

[1192] Sorting by Time

[1193] In a tabular display, where data can be sorted on multiplecriteria, the results of a sort may appear erroneous because the systemmeasures time in milliseconds, while NETSMART reports time in seconds.For example, the following Sort dialog shows the sorting criteria thatwere used to sort Fault Manager alarms information. First, the time thealarm was raised was selected and then the severity of the alarm wasselected. The resulting output looks to be incorrect for the 10:31:44time slot. The results of the sort in the following figure shows that acondition (NA) is inserted between two major alarms. The condition wasraised milliseconds before the second major alarm, so it appears in thelist before the second major alarm.

[1194] Ordering Sort Parameters

[1195] The order in which the Sort By buttons are selected willdetermine the sort order. The first (top) sort parameter has precedenceover the second, the second has precedence over the third, and so forth.When the sort takes place, the NMS Raise Time will be sorted first.Because the Ascending button wasselected, the sort will be from theearliest time to the most recent time. Next, the severity level of eachalarm will be sorted in descending order within each NMS raise time.Alarm conditions will be sorted next in descending order within eachseverity level (which was sorted within each NMS raise time). ServiceEffect is the last button selected, and will be sorted last. Because theAscending button is selected, the processing will sort service effectsin ascending order, within each condition.

[1196] Cutting and Pasting Information

[1197] Support for Copy and Paste is available in editable fields suchas the ones in Edit NE and the Raw TL1 editor, using the systemclipboard.

[1198] Use CTRL+C to copy the information, and CTRL+V to paste it into atext area. From tables, right clicking on a cell lets you see the textin a separate dialog. Select the text in this dialog that you want tocopy and press CTRL+C to copy. The text can then be pasted by pressingCTRL+V in a text destination field. There is no menu item or toolbartool to support this action.

[1199] Setting Column Displays

[1200] You can define which columns will be displayed and which will behidden in most tabular views. To display the Column Settings dialog,either click on the Columns tool in the toolbar or select ColumnSettings from the Operations menu. Use the Column Settings dialog tospecify display criteria. The order for column display can be changed byselecting the heading field and dragging the field to a differentposition in the display.

[1201] 1 Click on the Columns tool or select Column Settings from theOperations menu. The Column Settings dialog displays.

[1202] 2 By default, all columns are listed in the Visible Columns list.Click to select a column in the Visible Columns list and then select theHide button to move the column to the Hidden Columns list. To show ahidden column, click to select a column in the Hidden Columns list andthen select the Show button to move the column to the Visible Columnslist.

[1203] 3 Highlight a visible column and then use the Move Up or MoveDown button to move the order of the column in the list. This willchange the display order for the columns.

[1204] 4 Click Ok to confirm the column settings.

[1205] View Logs

[1206] Use the Log Managers to view NETSMART logs. Available logsinclude:

[1207] Activity Log Manager

[1208] Fault Manager

[1209] TL1 Log Manager

[1210] Transient Event Log Manager Each of these logs can be viewed fromthe NETSMART menu's Log Manager selection. All logs maintain a maximumof 30 days worth of records.

[1211] Note: There are two types of Sort dialogs. One type allows you tosort using a single argument, while another type (the Fault Manager, forinstance) allows you to select multiple sort arguments. In the secondtype (multiple arguments), it may sometimes appear that the data is notordered correctly.

[1212] View Activity Log

[1213] The Activity Log provides a summary list of operator activitiesand NE state changes. For performance reasons, the Activity Log isbuffered and the user may experience a delay of at least 1 minute beforethe log appears in the database. This delay is to accommodate transientlog messages. The Activity Log is sorted based on a descending timestamporder. The record with the newest timestamp is displayed first. Becausethe system measures time in milliseconds while NETSMART reports time inseconds, some sort ordering may appear erroneous.

[1214] 1 From the NETSMART menu, select Log Managers. From the menu,select Activity Log Manager to display the Activity Log Manager window.The selected log displays. By default, the Activity log is sorted inTimestamp Descending order.

[1215] Note: It takes approximately 30 seconds to 1 minute for an actionto be added to the Activity Log.

[1216] View Fault History Log

[1217] Once an NE alarm has been cleared, the record is stored in theFault History database. For performance reasons, the Fault History Logis buffered and the user may experience a delay of at least 1 minutebefore the log appears in the database. This delay is to accommodatetransient log messages.

[1218] 1 From the NETSMART menu, select Log Managers. From the cascadingmenu to the right of Log Managers select the Fault History Log Manager.The following window displays. The menu bar and toolbar for the FaultHistory Log Manager are identical to the Activity Log Manager.

[1219] View TL1 Commands

[1220] Both user-generated and NE-originated TL1 commands can be viewedin the TL1 Log.

[1221] 1 From the NETSMART menu, select Log Managers. From the cascadingmenu to the right of Log Managers select TL1 Log Manager.

[1222] View Transient Events

[1223] The Transient Log Manager allows viewing, filtering and sortingof all the Transient Condition events from the Fault History log.Transient Condition records are those that are reported but do not haveany clearing event associated with them. It is similar to the FaultHistory log manager except for the condition that is a Transient event.For performance reasons, the Transient Event Log report is buffered andthe user may experience a delay of at least one minute before the logappears in the database.

[1224] 1 From the NETSMART menu, select Log Managers. From the cascadingmenu to the right of Log Managers select Transient Log Manager. Thetoolbar and menu bar are the same the Activity Manager.

[1225] Introduction to Meta Model

[1226] This section provides overview and design information about MetaModel component of NETSMART. The Meta Model provides an instantiatedmeans of describing any specific network element and generic. The metamodel captures the physical and logical components that comprise the NE.

[1227] This meta model is used by the application to access metainformation for an NE and any specific instance of a component supportedby the NE. One challenge and objective for NETSMART is to provide ageneric solution for introducing new NE assemblies. The design of themeta model was intended to satisfy this goal. Other applications withinNETSMART also face this similar challenge.

[1228] It is been widely accepted that a network element suites ageneric assembly tree pattern very well. Ideally, applications like autodiscovery, auditing, reconciliation, database change handling,configuration management should all provide generic solutions (i.e.non-type specific). Type specific traversal is supported by the metamodel for those applications that find it difficult to designgenerically.

[1229] Scope

[1230] This document describes the NE Meta Model design with somecoverage on related applications (e.g. Autodiscovery). It does not coverdetails on aspects related to other components. It is acknowledged thatadditional requirements for the Meta Model will arise during theremaining development phases of NETSMART. The NE Meta Model is veryflexible and extensible. It is expected that as additional requirementsare identified they will be added to subsequent revisions of thisdocument.

[1231] Overview

[1232] This section provides an overview for the Meta Model component ofNETSMART. Meta Model is the core the data driven approach of NETSMART.Various semantic details of a network element are captured in MetaModel, such as different objects managed by network element (e.gshelves, equipment, facilities etc.), relationships between theseobjects, various attribute applicable to these managed objects etc. Thecontainment hierarchies between managed objects is also captured in MetaModel. The meta model provides a type of management information base forthe application. If something changes between two successive releases ofa network element, it can be handled in Meta Model by just incorporatingthese changes to the network element model. Following are few examplesof the kind of information captured in this component:

[1233] Equipment contained in a shelf

[1234] Different facilities available on a network element.

[1235] Different values which an equipment attribute can take

[1236] Working and Protect participant in an EPG or FFP

[1237] The following depict the major design objectives for the metamodel.

[1238] Easy introduction of new network elements.

[1239] Allow the applications to traverse the meta model hierarchicallyand generically.

[1240] Allow the applications to define various data model, and metamodel, relationships which will help satisfy their specificrequirements. Note: These may and probably will be unrelated to theassembly containment. For example, a MetaSection is a way to groupMetaSlot(s) for alarm correlation but a MetaSection has nothing to dowith the assembly hierarchy.

[1241] Provide the application with the ability to design using typedinterfaces while maintaining the models generically.

[1242] Each managed object on network element is represented by a MetaObject in the Meta Model which contains all relevant meta informationabout that managed object. There are different Meta Objects fordifferent type of facilities, equipment, EPGs etc. Each Meta Object fora given NE type in the meta model, is identified by Meta Instance Idwhich is just a label given to Meta Objects for identification. If thereare multiple Meta Objects of the same type (e.g. two STS1 facilities)which have same characteristics, they are mapped to the same MetaComponent. Meta Component represents ‘Type’ of Meta Object. Theattributes can be defined against a Meta Object as well as MetaComponent. Attributes defined against a Meta Component are applicable toall Meta Objects related to that Meta Component. All common attributesof similar Meta Objects are defined against Meta Component whereas, ifthere are any specific attributes applicable to a particular Meta Objectonly, they can be defined against Meta Object itself. Meta Model alsocaptures some information which does not pertain to network elementdirectly, for example the name of the java class to be used for addresstranslation for a particular NE is also captured in meta model.

[1243] In the overall picture of NETSMART, meta model resides inApplication Server. Configuration Manager is the main user of metamodel. All other components access meta model via Configuration Manager.The usage of meta model can be divided into two major parts:

[1244] Autodiscovery/Resync/Audit/Reconcile

[1245] Providing specific meta information

[1246] The meta model knows nothing about the current state of a networkelement. It maintains only a static representation of a network element.The Autodiscovery¹ application uses the meta model to drive the buildingof the dynamic view of the network element. Only the dynamic view of anetwork element provides current state. The dynamic view of a networkelement is captured in another component namely the ConfigurationManager. Fundamentally, the dynamic view of a network element is asubset of the meta model containment tree. During autodiscovery, thecontainment hierarchy modeled in meta model is used to build thecontainment tree (dynamic view) of application objects in ConfigurationManager. The containment hierarchy in meta model dictates thecontainment hierarchy in configuration manager. Only containmentrelationships in meta model are used for autodiscovery. Otherrelationships in the meta model relationship tree are not used duringautodiscovery.

[1247] Once autodiscovery is done, configuration manager can obtain anyspecific meta information from meta model. For example, while displayingequipment and ports in configuration manager GUI, configuration managerneeds to find out various ports supported by a particular equipment.This information is obtained by configuration manager from meta model onneed basis. Another example is that when user wants to change someprovisioning attribute on a facility or equipment, configuration managerGUI presents list of valid values for that attribute. This list of validvalues is obtained from meta model on need basis.

[1248] Meta Model can be divided into two parts on broad basis:

[1249] Meta Model Data

[1250] Meta Model Engine

[1251] Meta Model data contains all the static modeling informationabout the network element. It models all the Meta Objects, relationshipsbetween them, various applicable attributes on Meta Objects, validvalues for these attributes etc. This data is captured in oracledatabase tables as per the data model. Initially, this data is recordedin .db files, one corresponding to each table in data model. These .dbfiles are loaded into oracle database using some awk scripts duringNETSMART installation. Once this data is loaded into oracle data-base,during Application server startup this information is read by Meta Modelengine and cached in memory in form of relationship tree. Once loadedinto memory, Meta Model engine uses this cache for future refer-ence. Itis possible to delay loading of this information into memory Meta Modelengine is the executable part in meta model which implements all theinterfaces exposed. It also implements semantic interpretation of MetaModel data, loading of meta model data from database to memory.

[1252] Feature Dependencies

[1253] In order to be able to support autodiscovery, Meta Model isdependent on support from COMMS for that NE type.

[1254] Process Overview

[1255] This section addresses process of adding support for a newnetwork element assembly. Following are main steps involved insupporting new network element in netsmart from meta-model point ofview:

[1256] Understanding the network element: This involves reading thedocumentation (e.g. Architecture and design documents, TL1 documentetc.) available on network element to be supported. This helps build thegeneral understanding of the network element. This also involves tryingTL1 commands on the NE and/or interacting with NE people to clarify somebehavioral doubts.

[1257] Modeling meta objects and relations: This involves abstractingthe containment and other relation-ships between various objects to bemodeled. Various relationships and objects to be supported depends onthe NETSMART requirements. NETSMART RSA dictates the type and level ofsupport required in NETSMART for a network element. Please refer toAppendix A for list of various objects and relationships commonlymodeled for network assemblies. It may be required to modeled additionalrelationships or objects depending on the requirements defined by RSA.This object-relation-ship model is captured in meta_assembly.db file.

[1258] Modeling other characteristics of meta objects: This includesfilling up other.db files for support of network element in question.This includes meta_instance.db, meta_component.db, meta_property.db,meta_attribute.db, meta_attr_map, meta_collapsed_naming key andmeta_eqpt_type_map.

[1259] Implementing a data cache java class for fetching configurationinformation from network element during the process of Autodiscovery.

[1260] Testing autodiscovery for the network element.

[1261] Code review for the model.

[1262] Assumptions

[1263] Modeling of a new NE assembly assumes that the documentation forthe network element is available (e.g. NMIS, PDS etc). Also, it isassumed for modeling of new assemblies that access to network element isalso available.

[1264] Data Model

[1265] This section defines the data model which is used to instantiatethe meta model. The assemblies for all net-work element types supportedby NETSMART will be stored in the database (Oracle). A specific NE metamodel can be loaded into memory on demand or pre-loaded during theApplication Server initialization. SQL queries are used to retrieve theassembly data and instantiate the meta model. The data model has beenupdated for the 2.i release. Changes for 2.i included (a) adding newercolumns to existing tables (b) dropping columns which existed prior to2.i and (c) introducing new tables. Table and column definitions whichexisted prior to 2.i are mentioned in italics. This is expected to serveas a reference for developers.

[1266] The following sections describe the data model and how the metamodel uses it to instantiate a network element assembly:

[1267] Schema definition

[1268] Query model.

[1269] Schema Definition

[1270] The following tables are used to define all network elementassemblies which are managed by NETSMART. The meta model is built byquerying the following tables:

[1271] meta_component

[1272] meta_instance

[1273] meta_assembly

[1274] meta_class

[1275] meta_property

[1276] meta_attribute

[1277] meta_assembly_map

[1278] meta_collapsed_naming_keys

[1279] meta_attr_map

[1280] meta_eqpt_type_map

[1281] The following tables have been eliminated in 2.i:

[1282] meta_revision

[1283] meta_component

[1284] The Component table is the catalogue of all available part typesfor a network element. Each part for a given base network element (e.g.FACTR) is assigned an component identifier that is a unique primary keyto the Component table. Following table lists the different columns inthe table and their descriptions: Table Column Datatype DescriptionNE_BASE varchar2(32) The base network element identifier (e.g. FACTR).META_COMP_ID varchar2(32) A unique component identifier. APPL_CLASSvarchar2(75) The name of the java class used to create applicationobject during autodiscovery. META_CLASS_ID varchar2(32) An enumeratedmeta class identifier. This field references the meta_class table.APPLICATION_(—) varchar2(15) The type value used by TYPE the applicationfor this component. (e.g. EQPT, TP, etc.). COMM_TYPE varchar2(15) Thetype value used by the communications layer for this component. (e.g.EQPT, TP, etc.) There is not a one to one mapping with theAPPLICATION_(—) TYPE. NAMING_KEY varchar2(15) Some components have anaming key. It is analogous to the applications ComponentType in theRelative-ComponentID. (e.g. Shelf, Slot, Group, etc.). Any giveninstance of this component may provide a NAMING_(—) VALUE which is usedin combination with this naming key.

[1285] Constraints:

[1286] Primary key: NE_BASE, META_COMP_ID

[1287] Foreign key: META_CLASS_ID references meta_class(meta_class_id)

[1288] meta_instance

[1289] The Instance table is the inventory of all available parts. Aninstance refers to the particular existence of a component (MetaObject)in relationship tree identified uniquely by META_INST_ID for aparticular NE type. Table Column Datatype Description NE_BASEvarchar2(32) The base network element identifier (e.g. FACTR).META_INST_ID varchar2(32) A unique instance identifier for a specificcomponent. META_COMP_ID varchar2(32) This instance's componentidentifier. NAMING_VALUE varchar2(32) Specifies complete Component IDfor the meta object. INSTANCE TYPE varchar2(15) Indicates if instance isa standard MetaObject, a collapsed MetaObject or an expandable collapsedMetaObject. AUTO_CREATE a varchar2(16) Indicates when an instance getscreated. case-1: when the configuration permits it case-2: alwayscreated automatically case-3: created by default if no data objectexists

[1290] Constraints:

[1291] Primary key: NE_BASE, META_INST_ID

[1292] NE_BASE, META_COMP_IDreferences meta_component(NE_BASE,META_COMP_ID

[1293] instance_type can be in (‘single’, ‘expand’, ‘collapse’)

[1294] auto_create can be in (‘normal’, ‘auto_create’, ‘default_create’)

[1295] meta_assembly

[1296] The assembly table describes the complete hierarchicalcomposition of a network element assembly. The composition is based oninstance identifiers. The composition of an assembly uses namedrelationships (or edges) with possible conditional expressions. TableColumn Datatype Description NE_BASE varchar2(32) The base networkelement identifier (e.g. FACTR). PARENT varchar2(32) A instanceidentifier for a specific assembly component. This instance of acomponent is the direct predecessor to the corresponding NODE identifierin the assembly hierarchy. NODE varchar2(32) A instance identifier for aspecific assembly component. This NODE identifier is the successor tothe PARENT identifier. EDGE varchar2(32) The EDGE defines a namedrelationship between the PARENT and the NODE. The reasons and usage ofrelationships is dependent upon application usage. For instance theAutodiscovery application is primarily concerned with CONTAINMENT typerelationships. Refer to appendix A for various relationships modeled inmeta model. PRIORITY integer This determines the order in which rows arereturned from database at the time of loading meta model intoapplication memory. CONDITION varchar2(1024) The condition is anoptional expression which can be attached to an edge. The dynamicevaluation of the conditional expression must be evaluated to true inorder for the relationship between the PARENT and the NODE to hold.

[1297] Constraints:

[1298] Primary key: NE_BASE, PARENT, NODE, EDGE

[1299] Foreign key: (NE_BASE, PARENT) references meta_instance(NE_BASE,META_INST_ID)

[1300] Foreign key: (NE_BASE, NODE) references meta_instance(NE_BASE,META_INST_ID)

[1301] EDGE must be one of (‘IS_A’, ‘IS_A_DEFAULT’, ‘CONTAINS’,‘CONTAINS_ONE_OF’, ‘CONTAINS_ONE_OF_DEFAULT’, ‘CONTAINS_FOR_NAMING’,‘CONTAINS_AS_WORKING’,‘CONTAINS_AS_WORKING_DEFAULT’,‘CONTAINS_FOR_PROTECTING’, ‘IS_NAMED_BY’,‘SUPPORTS_PORT’, ‘SectionToEquipment’, ‘SectionEquipmentDefault’,‘SectionToType’, ‘HAS_PROT_PARTICIPANT’, ‘HAS_PROTECTING_PARTICIPANT’,‘HAS_WORKING_PARTICIPANT’, ‘IS_SUPPORTED_BY’, ‘IS_XCONNECTABLE_TO’,‘IS_DEFAULT_XCONNECTABLE_TO’, ‘IS_DEFAULT_(—)1WAY_XCONNECTABLE_TO’

[1302] meta_class

[1303] The meta_class table provides the information needed toinstantiate MetaObject(s). MetaObject(s) are the instantiatedrepresentation of a component instance. The MetaObject models staticinformation about a component. The MetaObject(s) are sub-classed (e.g.MetaShelf, MetaFunctionalGroup, MetaEquipment, etc.) and provide a typedhierarchical representation of an assembly. Table Column DatatypeDescription META_CLASS_ID varchar2(32) An enumerated meta classidentifier. META_CLASS varchar2(75) The actual JAVA class name,including package information. These classes are implemented in themeta_model package and are instantiated using JAVA reflection.

[1304] meta_assembly_map

[1305] The meta_assembly_map defines the assemblies managed by FENICS.It also provides for the mapping of assembly id. That is, a particularassembly can be managed as another. In addition, this table provides theweight assigned to a particular assembly, the managed level and autoload flag. Table Column Datatype Description. TYPE varchar2(32) Thenetwork element type as retrieved from the NE (e.g. FACTR). The completeassembly id consists of the TYPE, CONF, MAJOR, and MINOR fields (e.g.FACTR UPSR 05 02). TO_TYPE varchar2(32) Mapped network element type.MINMAJOR varchar2(5) The major and minor network element revision numberAUTO_LOAD varchar2(5) Flag indicating whether the mapped assembly shouldbe auto loaded during initialization. The following are not available in2.i: CONF The network element configuration as retrieved from the NE(e.g. UPSR). MAJOR The network element major revision as retrieved fromthe NE (e.g. 05). MINOR The network element minor revision as retrievedfrom the NE (e.g. 02). TO_BASE Map the above assembly to this basenetwork element id. (e.g. FACTR). The mapped assembly id consists of theTO_BASE, TO_MAJOR and TO_MINOR fields (e.g. FACTR 05 02). TO_MAJOR Mapthe above assembly to this major network element revision. (e.g. 05)TO_MINOR Map the above assembly to this minor network element revision.(e.g. 02) WEIGHT The weight assigned to the complete assembly id.MANAGE_LEVEL The managed level of the mapped assembly id (e.g. 5S)

[1306] Constraints:

[1307] Primary key:

[1308] AUTO_LOAD must be either ‘true’ or ‘false’

[1309] meta_property

[1310] The meta_property table captures the properties² for a specificcomponent. A property is a generic way of grouping attributes of acomponent. The grouping of attributes into properties is applicationdependent. For example, the attributes which are used to describe acomponents current state and configuration are grouped into theATTR_LIST property. Table Column Datatype Description NE_BASEvarchar2(32) The base network element identifier (e.g. FACTR).META_PROPERTY_ID varchar2(32) Unique identifier for the property.PROPERTY_NAME varchar2(32) The name assigned to this property. (e.g.ATTR_LIST) The following are not available in 2.i META_COMP_ID Thecomponent identifier which is associated with this property. This mayalso be a META_CLASS_ID. If it is a META_CLASS_ID, all instances of theparticular META_CLASS receive this property. PROPERTY_KEY A uniqueidentifier for a property name. Used to distinguish identical propertynames with conditions. CONDITION A condition expression which canoptionally be attached to the property. The dynamic evaluation of theconditional expression must be evaluated to true in order for thecomponent to access this property.

[1311] Constraints:

[1312] Primary key: NE_BASE, META_PROPERTY_ID

[1313] meta_attribute

[1314] The meta_attribute table captures the attributes for a specificproperty. The meta_attribute table provides the capability of describingthe characteristics of any given attribute. This table serves asinventory of different attributes applicable to NE types. Table ColumnDatatype Description NE_BASE varchar2(32) The base network elementidentifier (e.g. FACTR). META_ATTRIBUTE_ID varchar2(32) Uniqueidentifier for the attribute. PROPERTY_ID varchar2(32) Prior to release2.i, this column was called PROPERTY_(—) NAME.Together with NE_BASE,references meta_property(ne_base, meta_property_id) ATTR_NAMEvarchar2(32) The name assigned to this attribute. TYPE varchar2(10) Theapplication type of the attribute. For example, String, Integer,Boolean, Float, Enum. VALUE varchar2(256) Although the data model, andmeta model do not know the current state of any components attributes.Some attribute have a static value. This value is not expected tochange. DEFLT varchar2(20) The default attribute value. VALID_VALUESvarray called A list of valid values for this attribute. This isstr_list_t currently limited to 15 elements of maximum length 15. MINvarchar2(20) A minimum value for this attribute. Used for Integer andFloat only. MAX varchar2(20) A maximum value for this attribute. Usedfor Integer and Float only. INCR varchar2(20) A increment value for thisattribute. Used for Integer and Float only. READ_ONLY varchar2(5) Aboolean flag indicating whether this attribute may be changed or not.REQUIRED varchar2(5) A boolean flag indicating that this attribute isrequired.

[1315] The following are not available in 2.i: PROPERTYKEY A uniqueidentifier for a property name. Used to distinguish identical propertynames with conditions. ATTRKEY A unique identifier for an attributename. Used to distinguish identical attribute name with conditions.META_COMP_ID The component identifier which is associated with thisproperty. This may also be a META_CLASS_ID. If it is a META_CLASS_ID,all instances of the particular META_CLASS receive this property.CONDITION A condition expression which can optionally be attached to theattribute. The dynamic evaluation of the conditional expression must beevaluated to true in order for the component to access this attribute.

[1316] Constraints:

[1317] Primary key: NE_BASE, META_ATTRIBUTE_ID

[1318] Foreign key: (NE_BASE, META_PROPERTY_ID) referencesmeta_property(NE_BASE, META_PROPERTY_ID)

[1319] ATTRNAME is NOT NULL

[1320] TYPE must be in (‘String’, ‘Integer’, ‘Boolean’, ‘Float’, ‘Enum’,‘Class’)

[1321] READ_ONLY must be either in ‘true’ or ‘false

[1322] Valid values for REQUIRED must be either ‘true’ or ‘false’

[1323] meta_attr_map

[1324] This table is new for the 2.i release. It links meta_attributewith either meta_component or meta_instance. Table Column DatatypeDescription NE_BASE varchar2(32) The base network element identifier(e.g. FACTR). META_ID varchar2(32) Identifies the meta_component ormeta_instance to which the attribute is assigned, META_ATTRIBUTE_IDvarchar2(32) Unique identifier for the attribute. CONDITION An optionalcondition expression. The dynamic evaluation of the conditionalexpression must be evaluated to true for the component instance toaccess this attribute.

[1325] Constraints:

[1326] Primary key: NE_BASE, META_ID, META_ATTRIBUTE_ID

[1327] Foreign key: (NE_BASE, META_ATTRIBUTE_ID) referencesmeta_attribute(NE_BASE, META_ATTRIBUTE_ID)

[1328] Foreign key: (NE_BASE, META_ID) may reference either metainstance(NE_BASE, META_INST_ID) or meta_instance(NE_BASE, META_COMP_ID)

[1329] meta_eqpt_type_map

[1330] This table is new for release 2.i. contains a vendor ID/CLEI toequipment type mapping. Table Column Datatype Description NE_BASEvarchar2(32) The base network element identifier (e.g. FACTR). VENDOR_IDvarchar2(32) Vendor Id (or CLEI) that uniquely identifies an equipmenttype. NE_EQPT_TYPE varchar2(32) Equipment type. This doesn't have to beunique since different vendor IDs/CLEI codes can map to the sameequipment type.

[1331] Constraints:

[1332] Primary key: NE_BASE, VENDOR_ID

[1333] meta_collapsed_naming_keys

[1334] This table is new for release 2.i. Specifies for a collapsed metainstance what are its naming keys that must be resolved. E.g. thecollapsed object representing an ATM VC on the SONET ring, theunresolved naming key would be vci. Table Column Datatype DescriptionNE_BASE varchar2(32) The base network element identifier (e.g. FACTR).META_INST_ID varchar2(32) Specifies a given instance. Together withNE_BASE, references meta_instance(ne_base, meta_inst_id) NAMING_KEYvarchar2(15) This is similar to the application ComponentType in theRelativeComponentID (e.g. Shelf, Slot, Group etc.). MIN integer Theminimum valid value for the RelativeComponen-tID. MAX integer Themaximum value for the RelativeComponentID. INC integer Incremental valuefor the RelativeComponentID PREFIX varchar2(32) String that may have tobe prepended to the Relative- ComponentID. POSTFIX varchar2(32) Stringthat may have to be appended to the Relative- ComponentID. PRIORITYinteger A collapsed meta object may have multiple naming keys. Thisspecifies the relative priority. INHERITED varchar2(5) Specifies whethervalue for RelativeComponentID is inherited from ancestor.

[1335] Constraints

[1336] Foreign key: (NE_BASE, META_INST_ID) referencesmeta_instance(NE_NBASE, META_INST_ID)

[1337] INC should not be <0 or >MAX

[1338] INHERITED must be either ‘true’ or ‘false’

[1339] MAX should not be less than MIN

[1340] meta_tmp

[1341] This is a temporary table. It is used by Meta Model awhilepopulating its tables with data Table Column Datatype Description NAMEvarchar2(256) Used as a temporary work space during data load pro-cess.

[1342] meta_strings

[1343] Another temporary table. Table Column Datatype Description NAMEvarchar2(700) Temporary ID integer Used to identify NAME

[1344] Constraints:

[1345] Primary key: NAME

[1346] meta_revision

[1347] This table has been eliminated in release 2.i.

[1348] The meta_revision table captures the possible revisions ofcomponents. Since network elements have revisions this table allows forthe definition of the components which comprise a particular networkelement revision. Each network element revision must define a list ofvalid components which are used to define the assembly. Table ColumnDescription NE_BASE The base network element identifier (e.g. FACTR).META_COMP_ID The component identifier. MJ_REV The network element majorrevision which requires this component. (e.g. FACTR 05). This field isused in con-junction with the MN_REV. MN_REV The network element minorrevision which requires this component. (e.g. FACTR 05 02). This fieldis used in conjunction with the MJ_REV.

[1349] Query Model

[1350] This section describes database queries performed by Meta Modelto instantiate a network element assem-bly. The following sectionsdescribe how the meta model is built:

[1351] Retrieving the Assembly Data

[1352] Retrieving an Assembly Base

[1353] Retrieving the Assembly Root Node

[1354] Retrieving the Assembly Hierarchy

[1355] Each SQL statement and its corresponding result set are discussedbelow.

[1356] Retrieving the Assembly Data

[1357] SQL:

[1358] SELECT * from meta_assembly_map;

[1359] Results:

[1360] The result is a collection of MetaAssemblyData objects. Thiscollection of MetaAssemblyDatadefine the net-work element assemblieswhich are managed by FENICS. This collection also provides a way to mapa par-ticular assembly to another. That is, to manage a particularassembly as if it was another. For example, FACTR 05 02 may be managedas a FACTR 05 01. Each MetaAssemblyData assigns a weight to aparticu-lar assembly. In addition, the managed level and auto load flagis provided in the MetaAssemblyData.

[1361] Retrieving an Assembly Base

[1362] SQL:

[1363] SELECT mi.meta_inst_id, mi.meta_comp_id, mi.naming_value,mc.appl_class, mc.meta_class_id, mc.application_type, mc.comm_type,mc.naming_key, mc.auto_create, ml.meta_class

[1364] FROM meta_instance mi, meta_component mc, meta_class ml

[1365] WHERE mi.ne_base=:1 AND

[1366] mc.ne_base =mi.ne_base AND mc.meta_comp_id =mi.meta_comp_id AND

[1367] ml.meta_class_id=mc.meta_class_id;

[1368] Results:

[1369] The result of this query is all of the components for a specifiedbase assembly. This becomes a cache of Met-aNode(s) which is used by theindividual assemblies under the base.

[1370] Retrieving the Assembly Root Node

[1371] SQL:

[1372] SELECT mi.meta_inst_id, mi.meta_comp_id, mi.naming_value,mc.appl_class, mc.meta_class_id, mc.application_type, mc.comm_type,mc.naming_key, mc.inherited_nk, mc.auto_create, ml.meta_class

[1373] FROM meta_instance mi, meta_component mc, meta_revision mr,meta_class ml

[1374] WHERE mi.meta_inst_id=:1

[1375] AND mc.meta_comp_id=mi.meta_comp_id

[1376] AND mc.ne_base=mi.meta_inst_id

[1377] AND mr.meta_comp_id=mi.meta_comp_id

[1378] AND mr.ne_base=mi.meta_inst_id

[1379] AND mr.mj_rev=:2

[1380] AND mr.mn_rev=:3

[1381] AND ml.meta_class_id=mc.meta_class_id;

[1382] Results:

[1383] The result of this query is a particular revision of a networkelement assembly. This is expected to return the single result setassociated with a particular base, major and minor revision of anassembly. This result set is used to create the MetaNe root node in theassembly hierarchy.

[1384] Retrieving the Assembly Hierarchy

[1385] SQL:

[1386] SELECT ma.ne_base, ma.parent, ma.node, ma.edge, ma.condition

[1387] FROM meta_assembly ma, meta_instance mi, meta_revision mr

[1388] WHERE ma.ne_base=:1 AND

[1389] ma.parent=:2 AND

[1390] mi.ne_base=ma.ne_base AND

[1391] mi.meta_inst_id=ma.node AND

[1392] mr.ne_base=ma.ne_base AND

[1393] mr.meta_comp_id=mi.meta_comp_id AND

[1394] mr.mj_rev=:3 AND

[1395] mr.mn_rev=:4;

[1396] Results:

[1397] The result of this query are the successors to the specifiedparent and ne_base parameters. This SQL is recursively called in orderto build the assembly hierarchy. It is started at the root MetaNe nodeand traverses depth first until it reaches leaf nodes and the entiretree is instantiated. NOTE: This is the most expensive, time consuming,part of building the meta model.

[1398] Retrieving Object-Attribute Assignment

[1399] SQL:

[1400] Please refer to LOAD_ALL_OBJECTS_ATTR_MAP insideMetaObjectLoader.java

[1401] SELECT mi.meta_inst_id, mam.meta_attribute_id, mam.condition,ma.meta_property_id

[1402] FROM meta_instance mi, meta_attr_map mam, meta_attribute ma

[1403] WHERE mi.ne base=:1 AND

[1404] ((mi.meta_inst_id=mam.meta_id) OR (mi.meta_comp_id=mam.meta_id))AND

[1405] mam.ne_base=mi.ne_base AND

[1406] mam.meta_attribute_id=ma.meta_attribute_id AND

[1407] ma.ne base=mi.ne_base

[1408] Results:

[1409] Loads all attribute_id values for every component inside anassembly.

[1410] Retrieve a Specific Object in an Assembly

[1411] SQL:

[1412] Please refer to LOAD_INSTANCE in MetaObjectLoader.java

[1413] SELECT mi.meta_inst_id, mc.meta_comp_id, mi.naming_value,mc.appl_class, mc.meta_class_id, mc.application_type, mc.comm_type,mc.naming_key, mi.auto_create, mcl.meta_class, mi.instance_type

[1414] FROM meta_instance mi, meta_component mc, meta_class mcl

[1415] WHERE mi.ne_base=:1 AND

[1416] mi.meta_inst_id=:2 AND

[1417] mi.meta_comp_id=mc.meta_comp_id AND

[1418] mc.ne_base=mi.ne_base AND

[1419] mc.meta_class_id=mcl.meta_class_id

[1420] Results:

[1421] Loads a specific object in an assembly.

[1422] Loading an Attribute for an Assembly Component

[1423] SQL:

[1424] Please refer to LOAD_OBJECT_ATTRIBUTES in MetaObjectLoader.java

[1425] SELECT ma.ne_base, ma.meta_attribute_id, ma.meta_property_id,ma.attrName, ma.type, ma.value, ma.deflt, ma.valid_values, ma.min,ma.max, ma.inc, ma.read_only, ma.required, mam.condition

[1426] FROM meta_instance mi, meta_attr_map mam, meta_attribute ma

[1427] WHERE mi.ne_base=:1 AND mi.meta_inst_id=:2 AND((mi.meta_inst_id=mam.meta_id) OR (mi.meta_comp_id=mam.meta_id)) ANDmam.ne_base=mi.ne_base AND mam.meta_attribute_id=ma.meta_attribute_idAND ma.ne_base=mi.ne_base

[1428] Results:

[1429] Loads all meta_attributes of a specified object in a givenassembly for a particular network element.

[1430] Loading Specific Object in an Assembly

[1431] SQL:

[1432] Please refer to LOAD_INSTANCE inside MetaObjectLoader.java

[1433] SELECT mi.meta_inst_id, mc.meta_comp_id, mi.naming_value,mc.appl_class, mc.meta_class_id, mc.application_type, mc.comm_type,mc.naming_key, mi.auto_create, mcl.meta_class, mi.instance_type

[1434] FROM meta_instance mi, meta_component mc, meta_class mcl

[1435] WHERE mi.ne_base=:1 AND.

[1436] mi.meta_inst_id=:2 AND

[1437] mi.meta_comp_id=mc.meta_comp_id AND

[1438] mc.ne_base=mi.ne_base AND

[1439] mc.meta_class id=mcl.meta_class_id

[1440] Results:

[1441] Loads a specific meta_instance object by relating themeta_instance with meta_class and meta_component.

[1442] Retrieve Assembly for a Network Element

[1443] SQL:

[1444] Please refer to LOAD_ASSEMBLY in MetaObjectLoader.java

[1445] SELECT parent, node, edge, condition, priority from meta_assemblyWHERE ne_base=:1 ORDER BY parent, priority, node

[1446] Results:

[1447] Loads the ordered assembly data for a specific network element.

[1448] Retrieving meta_collapsed_naming_keys

[1449] SQL:

[1450] Please refer to LOAD_ALL_COLLAPSED_NAMING_KEYS inMetaObjectLoader.java.

[1451] SELECT * from meta_collapsed_naming_keys where ne_base=:1 ORDERby priority;

[1452] Results:

[1453] Loads information that will help to resolve naming_keys for acollapsed meta instance.

[1454] Meta Model

[1455] The MetaModelFactory is a singleton object which requiresinitialization in each process space that requires meta model access.The MetaModelFactory creates a MetaBaseAssembly for each base networkelement supported by the system (e.g. FACTR, FLM150, etc.). In addition,the MetaModelFactory assigns MetaAssembly(s) to each MetaBaseAssemblyreflecting the network element revisons that are supported by NETSMART(e.g. FACTR 05 01, FACTR 05 02, FLM150 11 02, FLM150 12 02, etc.). EachMetaAssembly evaluates its auto load flag. If it is True, theMetaAssembly will initiate the instantiation of the assembly. Theinstantiation of the assembly starts at the MetaNe root node andinstantiates a tree of MetaNode(s). The tree of MetaNode(s) includenamed relationships between nodes called MetaEdge(s).

[1456] Each MetaEdge may have a condition expression which must beevaluated to true in order for the relationship to be valid. Theinstantiated assembly provides an application information base for anetwork element. It is static network element data that is used forautodiscovery, configuration management and various other applicationcomponents. The assembly tree may be traversed generically or via atyped interface.

[1457] If the auto load flag is False, the MetaNe root node is the onlynode that is instantiated. The rest of the assembly tree is instantiatedon demand by the Application. The Application which requires access toan assembly obtains it via a MetaNeFactory. The Application provides thenecessary data to identify an assembly and acquires a MetaNe reference.If the assembly was not auto loaded it is loaded at this time. FIG. 38shows the MetaModel class diagram for this process.

[1458] Meta Base Assembly

[1459] The MetaBaseAssembly represents a base network element (e.g.FACTR).The MetaBaseAssembly is multithreaded and synchronized and iscreated during process initialization. MetaBaseAssembly has state whichis represented by MBA_State. At the time of initialization, the state isset to MBA_Inactive. If Meta-BaseAssembly is auto load, aMetaBaseAssemblyLoader is created and the state gets transitioned toMBA_Loading. If it is not a case of auto load, then it is loaded ondemand. The MetaBaseAssembly is only loaded once in the process space.If there is a second request to load a MetaBaseAssembly in MBA_Loadingstate, the invoker is blocked until loading is complete. MBA_NotFoundrepresents absence of MetaBaseAssembly in database. When the load issuccessful, the state is transitioned to MBA_Loaded.

[1460] If load fails due to some reason, the state is transitioned toMBA_Not_Loaded. FIG. 39 shows the MetaBase Assembly class diagram. FIG.40 shows the Meta Base Asembly state transition diagram.

[1461] Meta Object

[1462] The MetaNode is an abstration which allows forgeneric/hierarchical traversal of a network element assembly. The MetaNeis the root MetaNode. The typed specific behavior is defined by theMetaObject subclasses. A MetaObject is a generalization of the thingsthat comprise a network element. The MetaObject may contain properties,or lists of attributes, called MetaProperty(s). The MetaPropertycontains MetaAttribute(s). The MetaProperty and MetaAttribute maycontain a Condition. The Condition must be evaluated at run time withcontext. Only if the Condition is true does the MetaObject recognizethat MetaProperty or MetaAttribute. A MetaObject is created by theMetaReflector using Java reflection. The MetaObject is a abstract classused to define generic behavior for typed network element objects. Thenetwork element assembly is a generic tree pattern implemented by theMetaNode and MetaEdge relationships. The network element assembly isalso typed. Each MetaNode is implemented as a MetaObject and subclass.FIG. 41 shows the MetaNode class diagram.

[1463] Loading a Meta Assembly

[1464] The network element assembly is a generic tree patternimplemented by the MetaNode and MetaEdge relationships. The networkelement assembly is also typed. Each MetaNode is implemented as aMetaObject and subclass. At the time of meta assembly loading, objectsand relationships are retrieved from the meta_assembly database tableand a relationship tree is constructed in application address space.

[1465]FIG. 42 depicts a small portion of a FACTR assembly. Starting atthe root MetaNode (e.g. FACTR_(—)5_(—)2), the meta model ishierarchically built depth first. The root node contains a PHYSICAL_SIDEand a LOGICAL_SIDE. From the PHYSICAL_SIDE, the hierarchy continues byworking its way down through the shelves, sections and equipments, etc.

[1466] The hierarchy of the assembly is totally driven by the datamodel. The loading of the meta model is strictly a reflection of whathas been modelled in the meta_assembly table.

[1467] Note the relationships between any predecessor and its successorsare named and may optionally have a conditional expression on them. Thecondition expression is evaluated dynamically at run time. The conditionmust be evaluated to true in order for the relationship to exist.

[1468] Objects & Relationships Modelled in Meta Model

[1469] This section provides list of various objects and relashionshipsmodelled in meta model. The list of objects and relashioships providedhere covers most of the common scenarios which apply to most of networkassemblies. It is important to understand that need for modelling newobjects and relationships may arise in future depending on the assemblyand the kind of support required in NETSMART for that assembly.Depending on the kind of support provided for an assembly, everyrelationships object may not be applicable. Following is the list ofcommonly modelled objects in meta model:

[1470] Shelves

[1471] Equipment

[1472] Facilities³

[1473] Equipment Protection Groups

[1474] Facility Fibre Protection Groups

[1475] Functional Groups

[1476] Clocks

[1477] CPU

[1478] In addition to that, there are some pseudo objects which can bemodelled to organize the hierarchy better. These objects are Sectionsand Groups. Sections are primarily used to group related equipmenttogether and Group is a more general notion to group set of related metaobjects together in meta_assembly. Following is list of relationshipsmodelled in meta model:

[1479] CONTAINS Used to model containment between two objects.

[1480] CONTAINS_ONE_OF If a parent object in the containment hierarchycan have only one of possible children (in dynamic view) then thisrelationship is used between parent object and individual childrenobjects.

[1481] CONTAINS ONE_OF_DEFAULT Used to relate a parent object to thechild object which will be default child in case when multiple childrenobjects are related to the parent by CONTAINS_ONE_OF rela-tionship.

[1482] IS_SUPPORTED_BY Used to capture relationship between functionalgroups and slots supporting those groups.

[1483] HAS_WORKING_PARTICIPANT Used to capture relationship between aprotection group (equipment or facility) and working object in thatgroup.

[1484] HAS_PROTECTING_PARTICIPANTUsed to capture relationship between aprotection group (equipment or facility) and protecting object in thatgroup.

[1485] SUPPORTS_PORT Used to capture relationship between port andequipment supporting that port.

[1486] IS_XCONNECTABLE_TO Used to model the relationship between twotime slot groups which can have cross con-nects between them. Used incase of FLASH192 only at present.

[1487] IS_DEFAULT_XCONNECTABLE_TOUsed to model the relationship betweentwo time slot groups which can have cross connects between them bydefault. Used in case of FLASH192 only at present.

[1488] IS_DEFAULT_(—)1WAY_XCONNECTABLE_TOUsed to model the relationshipbetween two time slot groups which can have one way cross connectsbetween them by default. Used in case of FLASH192 only at present.

[1489] CONTAINS_AS_WORKING Used to model relationship between linetermination point and working time slot groups contained in it.

[1490] CONTAINS_AS_WORKING_DEFAULT Used to model relationship betweenline termination point and default working time slot groups (if any)contained in it.

[1491] CONTAINS_FOR_PROTECTING Used to model relationship between linetermination point and protecting time slot groups contained in it.

[1492] Modelling Tips

[1493] Following are some tips and guidelines for modeliing of networkelements:

[1494] MetaObjects to represent CPUs have to be named as<string1>-<string2> While <string1> can be anything (usually “Cpu” or“CPU”), <string2>has to be the AID of the CPU. Because this is the logicused to get the CPU aid during a SWDL/RMBU! The existing metamodelsfollow this rule.

[1495] There are MetaObjects for which we will not create anyapplication object in the dynamic tree. Exam-ples are PHYSICAL_SIDE,LOGICAL_SIDE, CPUs etc. You can give ‘none’ as their naming_value inmeta_instance.db Also make sure that you leave the naming_key of thecorresponding meta component entry as empty.

[1496] Any MetaObject contained by another MetaObject that has beenmarked as ‘expand’ (ie, instance_type is ‘expand’ in meta_instance.db)should itself be given the instance_type ‘expand’.

[1497] Any MetaObject contained by another MetaObject that has beenmarked as ‘collapse’ (ie, instance_type is ‘collapse’ inmeta_instance.db) should itself be given the instance_type ‘collapse’.

[1498] Make sure that CID+Type will be a unique key to identify aMetaObject. CID is the naming_value col-umn in meta_instance. And Typeis the comm_type column in meta_component. In other words, there shouldnot be more than one MetaObject with the same CID and the same Type.

[1499] While assigning the meta attribute LINKABLE to MetaObjects, doNOT use any conditions. This is because when Topology queries CM for alllinkable facilities, CM does a direct DB query by joining pnecomponenttable with metamodel tables. Conditions cannot be evaluated during this.Again, existing metamodel does not use conditions for LINKABLE attr; sowe can keep it that way.

[1500] Now we can assign meta attributes to meta_component_id's ormeta_instance_id's. So it is better to keep these two ids distinct.

[1501] Use comments generously in the db files. It would be useful lateron, if we can put the schema of the corresponding table at the beginningof each db file.

[1502] Try to organize the db files into different logical blocks. Useblank comment lines to visually separate diff blocks. Give usefulcomments for each block. For examples, p1 see FLM600/*.db files.

[1503] Conditions and Their Evaluation

[1504] While modelling a network element assembly, conditions can beused where ever some concept is applicable based on condition. Incurrent design following things can be qualified with conditions:

[1505] Relationship between two meta objects could be conditional. Whilemeta model relationship tree tra-versal, relationships qualified withconditions are only traversed if the condition is met. Traversal logicdoes not reach a node, if there was a condition on its predecessor edge(i.e. relationship to parent) which is evaluated to ‘false’. Similarlogic applies to traversal from a child to parent object as well. Thiskind of conditional relationships are covered in meta_assembly.

[1506] Applicability of an attribute to a Meta Component or MetaInstance could be conditional. An attribute and all its characteristics(e.g. vaild values, read only etc) will apply to a Meta Component orMeta Instance only if the associated condition (if any) evaluates totrue. The conditions in meta model look likeDataObject.getAttributeValueString(“CONF5”)=“D1” This implies that ifthe value of attribute ‘CONF5’ is equal to ‘D1’ in an object of classDataObject then this will evaluate to ‘true’. In order to evaluateconditions, meta model needs ‘context’. A component which invokes aninterface on meta model, needs to provide context as well so that metamodel can evaluate any related conditions. ‘Context’ is a genericconcept and is a vector of objects. In the example of condition above,the ‘context’ is expected to be a vector of DataObject⁴ objects. Theframework component responsi-ble for evaluation of conditions, willinvoke ‘getAttributeValueString(“CONF5”)’ method on each object incon-text and compare the return value with ‘D1’. If there was any objectin the context for which this comparison succeeds the condition will beevaluated to true.

[1507] Autodiscovery Overview

[1508] This section presents overview of the autodiscovery process andinvolvement of meta model in this process. When user adds a networkelement and performs ‘login’ from NETSMART GUI, ACT-USER TL1 command issent by NETSMART to log into the network element. Autodiscovery processis triggered, once successful login and some basic initialization isachieved. Autodiscovery process can be divided into three major phasesas described below:

[1509] 1. Retrieving configuration information from the NE beingautodiscovered—During this phase all con-figuration information isretrieved from network element by sending appropriate TL1 commands forretrieval (e.g. RTRV-EQPT etc.). Communication Server providesinterfaces to the application server for these TL1 commands. As a resultof invocation of these interfaces on COMMS, Application Server getscollection of dataobjects. COMMS returns one dataobject for each aidfetched from the network element. These dataobjects are created by COMMSafter parsing the TL1 responses. Each KEYWORD-DOMAIN pair in TL1response is translated to a Attribute-Value pair. Each dataobjectcontains collection of such Attribute-Value pairs. In addition tocollection of Attribute-Value pairs, dataobject also contains aid andComponentID⁵. During this phase information about all entities (i.e.equipment, facilities, EPGs etc) is retrieved from network element. Thisinformation retrieval is driven by DataCache. Their are subclasses ofDataCache for each NE type supported by NETSMART. For example, there isFACTRDataCache which drives this information retrieval for FACTR NEsduring Autodiscovery. It is responsibility of the meta model person whois modelling a new NE type to imple-ment a subclass of DataCache forthat NE type. From the dataobjects received from COMMS, the DataCachebuild a hashmap of these dataobjects with CompinentID being the key.DataCache also supports interface to obtain a dataobject based on itsComponentID, which is used by Autodiscovery in second phase.

[1510] 2. Traversing the meta model relationship tree and creatingapplication objects 2—Once the DataCache has retrieved all theinformation and built a hashmap of dataobjects, Autodiscovery traversesthe meta model relationship tree and creates application objects. Theseapplication objects are passed to Configuration Manager, which holds andmanages them. The traversal starts from the root node and for every nodefollowing steps are taken to create application objects:

[1511] If the meta object is marked as auto_create (i.e. auto_createcolumn in meta_instance is set to ‘auto_create’ for the meta object)then a default application 3 object is created for that meta object.

[1512] If the meta object is marked as normal (i.e. auto_create columnin meta_instance is set to ‘normal’ for the meta object) thenComponentID for that meta object is obtained. If there is a dataobjectfor this ComponentID in the DataCache then an application object iscreated for the meta object using

[1513] 1. ComponentID is internal to NETSMART and can be treated as aunique identifier for a dataobject for a given TID. AddressTranslator inCOMMS translates the aid in TL1 response to corresponding COmponentID byfollowing some predefined rules.

[1514] 2. Application objects are held by Configuration Manager. Eachapplication object hold reference to corre-sponding meta object and dataobject.

[1515] 3. In default creation a dummy data object is created in order.the dataobject otherwise no application object is created correspondingto the meta object.

[1516] If the meta object is marked default_create (i.e. auto_createcolumn in meta_instance is set to ‘default_create’ for the meta object)then ComponentID for that meta object is obtained. If there is adataobject for this ComponentID in the DataCache then an applicationobject is created for the meta object using the dataobject otherwise adefault application object is created.

[1517] 3. Configuration Manager builds a containment tree of applicationobjects created by Autodiscovery. The containment relations in this treeof application objects (also called as dynamic tree or dynamic view ofthe NE) are same as modelled in meta model. When autodiscovery passes anapplication object to configuration manager, it also passes reference ofparent application object.

[1518] Collapsed Meta Objects

[1519] Collapsed Meta Objects are specialized Meta Objects whichrepresent multiple objects of the same type. The behavior of a collapsedMetaObject similar to a standard MetaObject with one major difference. Astandard MetaObject has a fully qualified ComponentID, invoking getCID() will return a complete ComponentID (e.g shelf=NBS-1:slot=CH-1:port=3).However, a collapsed MetaObject can not return a fully qualifiedComponentID because it represents multiple objects. For thoseRelativeComponentIDs that cannot be resolved, a wildcard value (‘*’), isreturned (e.g. group=1:sts=1:vtg=*:vt=*, group=4:sts=1:vpi=0:vci=*).

[1520] However, any ComponentID will always resolve to a MetaObject. Forexample, ComponentID group=1:sts=1:vtg=2:vt=4 will resolve to theMetaObject with ComponentID group=1:sts=1:vtg=*:vt=*. Note thatComponentID group=1:sts=1:vtg=3:vt=2 would also resolve to the sameMetaObject.

[1521] To determine if a MetaObject is a collapsed object, a newinterface has been provided on MetaObject: isCollapsedObject( ).

[1522] A collapsed MetaObject can be designated as “expandable”. Unlikethe previous version of the MetaModel, expansion in this case does notmean replicating the MetaObject ntimes. Instead, the collapsedMetaObject will fully expand all possible ComponentIDs and that list ofexpanded CIDs can be retrieved via a new MetaObject interfacegetAllInstances( ). For collapsed MetaObjects not designated as“expandable”, an attempt to retrieve all possible ComponentIDs willreturn an empty list. To detemine if a collapsed MetaObject isexpandable an application can invoke the MetaObject interface:isExpandedObject( ).

[1523] Summary of the interfaces changed or added on MetaObject.java tosupport collapsed objects:

[1524] ComponentID getCID( )

[1525] In the case of a normal MetaObject getCID( ) will return thefully resolved ComponentID. If it is a col-lapsed MetaObject, whetherthat MetaObject is expandable or not, the ComponentID returned will notbe fully resolved. Wild card values will appear for thoseRelativeComponentIDs that could not be resolved.

[1526] boolean isCollapsedObject( )

[1527] Return true if the MetaObject is a collapsed object; falseotherwise.

[1528] boolean isExpandedObject( )

[1529] Returns true if the MetaObject is a collapsed object and itsComponentID can be fully expanded to all possible ComponentIDs.

[1530] Vector getAllInstances( )

[1531] If the MetaObject is a collapsed object and it can be expanded,then a list containing the fully expanded list of ComponentIDs isreturned. Otherwise an empty list is returned. In most casesapplications will not care about whether the MetaObject is collapsed ornot since all other interfaces remain unchanged. Applications that aremost likely to be affected are those that create and main-tain the NEconfiguration (e.g. autodiscovery, configuration or provisioningchanges).

[1532]FIG. 34 shows architecture components for an embodiment of thedisclosed innovations. Oracle databases are used for persistent storage,accessed via SQL (Structured Query Language). Lower applicationsinterface to the databases through FDBC (Fujitsu DataBase Connectivity)and use FORA (Fujitsu Object Relational Adaptor) for mapping objects tothe database.

[1533] The network manager applications include topology (used to managegroups, NEs, and links), a software repository, a fault manager thatmanages fault for the network, raw TL1 and TL1 batch that provide rawTL1 interfaces and batch capability, and software download and remotebackup manager.

[1534] The element manager applications include a meta model thatdescribes an NE for a given release, autodiscovery that identifies anddiscovers NEs, configuration manager for the NEs, crossconnect managerthat manages the NE crossconnects, a fault manager, and softwaredownload and remote backup manager for the NEs.

[1535] The framework components include event service, query and clientpersistency which provides object query service and column query serviceto the client, transaction and concurrency which provides transactionservices, security, thread which provides threading policy and CORBArequest dispatching, connection (Life Cycle Service) which providesservices for server activation, log and trace, directory naming service(used to locate server object), and cluster agent framework whichprovides HA services and process management. The communication subsystemincludes a session manager that manages the TL1 sessions to NEs, asession which provide TL1 sessions to NEs and performs CORBA IDL to TL1command/response and autonomous message mediation, a raw session, anaddress manager that provides TID to network address mapping (source canbe TARP or NETSMART database), and an OSI.

[1536] Process Architecture

[1537]FIG. 35 shows an overview of the process architecture forNETSMART. NETSMART process architecture is divided into CORBA services,Framework, Process Activation and Monitoring, Application, andCommunications.

[1538] The CORBA services include Naming Service (provides nameresolution service for NETSMART CORBA objects), Event Service (providesCOS event channels for autonomous communication in NETSMART), and orbixd(orbix demon provides CORBA client/server connection management for theobject request broker).

[1539] The Framework core includes Framework and Security. Frameworkconsists of a LogManager (provides high speed logging service toNETSMART application components), Broker (provides CORBA object locationand activation services to application components), Client Persistency(provides remote persistency services to GUI client) and Client Query(provides remote Query service to GUI Clients). Security consists of aUser Manager (provides management of NETSMART users), Access ControlManager (provides management of user security profiles to control accessto NETSMART functionality), and User Session Manager (manages all activeNETSMART sessions).

[1540] Process Activation and Monitoring consists of the fenicsd anddaemon monitor. NETSMART daemon processes monitor the health of allNETSMART processes, and identify process failure and restart them. Thefenicsd an daemon monitor also monitor each other and relaunch of one ofthem dies.

[1541] Optional application services include UPS manager (listens totrap notifications from the UPS for power down events, and manages theshutdown of NETSMART under power failure conditions), emlnml server(provides an interface to NETSMART for NML systems), and performancemanagement (collects performance data from the NES and persists theminto Oracle database for later analysis.

[1542] Core application services include the topology server (providesinterfaces to manage NEs, groups, and links; provides services toestablish raw TL1 sessions to the NEs, and provides integrated networklevel fault query, management, and count service), the applicationserver (various components of which perform the following: model thephysical NE; manage NE configuration in databases; maintain the metadatafor each type of NE managed by NETSMART; use static metamodel definitionto instantiate NE specific objects by fetching information from thephysical NE; identify discrepancies and reconcile the differencesbetween the physical NE and the NETSMART view of the NE; managecrossconnects in database and the physical NE; and store the NEs faultsin databases), and the software manager server (which provides servicesto manage software generics, provides NE level services to download andactivate software generic, and back-up/restore of NE database; theseinterfaces are provided at the network level).

[1543] Core communication services include the communication server(provides command/response/event and raw TL1 sessions to the NEs, andprovides IDL to TL1 and vice-versa mediation), the session manager(manages communication sessions to NEs and provides a lookup servicefrom TID to NSAP/IP). Communication may be provided via TARP (TargetAddress Resolution Protocol), FTAM (File Transfer and AccessManagement), and OSI standards.

[1544]FIG. 36 shows a hardware architecture for an embodiment of thepresently disclosed innovations. The Enterprise-5500/6500 configurationshows one example of hardware implementation for the server. The servernetworks with individual NEs by a 100 base-T NE communication network,and with client machines via a client communication network, using OSIand IP LAN cards respectively. The server also has an uninterruptablepower supply (UPS) and an L280 Autoloader backup system connected by asmall computer system interface (SCSI). This figure shows the framework,applications, and communications blocks of the server. Oracle databaseusing redundant array of inexpensive disks (RAID) serves as persistentbackup.

[1545]FIG. 37 depicts the server architecture for a given NETSMARTapplication component. An application component (for example, topologyserver, communication server, etc.) interfaces with the Oracle databasethrough FDBC and uses FORA for mapping objects to the database. FDBCuses JNI (Java Native Interface) to call OCI (Oracle Call Interface)functions. OCI functions are written in C and allow databasemanipulation and management.

[1546] The thread filters define the threading semantics for a givenapplication. Thread filters are used to deliver CORBA requests to CORBAobjects.

[1547] The utilities are available for various tasks. They includeasyncworker (the worker thread pattern that executes user commandsentered through the GUI), object pool (a pattern for optimal performancecontaining a pool of objects which can be reused), inventory (lists ofrelated objects), licensing service (restricts usage of installationbased on the NETSMART licensing purchased by the user), task management(pattern for multi-thread programming), and collection (extension andJava collection, generates collection objects to transmit over CORBA).

[1548] The helpers include DNSHelper (Directory Naming Service, used tolook up CORBA objects in NETSMART), authenticator (providesauthentication services when users request restricted privileges),eventservice (asynchronous communication between various components inNETSMART), registry (lookup service for CORBA for objects in NETSMART),and log/trace (logging and tracing to NETSMART application components).

[1549] Definitions:

[1550] Following are short definitions of the usual meanings of some ofthe technical terms which are used in the present application. (However,those of ordinary skill will recognize whether the context requires adifferent meaning.) Additional definitions can be found in the standardtechnical dictionaries and journals.

[1551] The NETSMART terminology may have meanings that are slightlydifferent from standard telephony terms. The terms used are definedbelow.

[1552] Access identifier (AID)—AIDs are address information identifyinga specific equipment slot or facility (traffic or overhead channel).

[1553] Bidirectional line-switched ring (BLSR)—A BLSR is a ring thatprovides working and protection fibers between nodes. If the workingfiber between nodes is cut, traffic is automatically routed onto theprotection fiber.

[1554] Common Language Equipment Identifier (CLEI®)—CLEI is a standardcode used by suppliers to identify equipment parts and systemconfigurations.

[1555] Correlation tag (CTAG)—CTAGs are required by TL1 and are used tocorrelate the input TL1 and response messages.

[1556] Equipment protection group (EPG)—The EPG is used to establish theworking/protection relationship between two cards.

[1557] Equipment—Equipment consists of the NEs and related hardwarewithin the telecommunications network.

[1558] Facility—The facility is the fiber or copper transmission mediaused between NEs to transport telecommunications signals.

[1559] Fiber facility protection (FFP)—FFP is used to establish aworking/protection relationship between two or more facilities.

[1560] Fujitsu minimum support NE—A Fujitsu NE that is not on theofficially supported list but conforms to a basic set of TL1 commandswill be managed as a minimally supported Fujitsu NE. Support consists oflogging on, adding links, displaying as an icon on the topology map, anddisplaying alarms.

[1561] Group—Groups are logical associations of NEs to facilitate NEmanagement. For example, NEs can be placed in a group based on locationor type of NE.

[1562] Tool Action/Function Previous Select Previous to return to theprevious displayed topic. Next Select Next to reverse direction andreturn to the topic where you first used Previous, one topic at a time.Print Displays the Print dialog and allows you to print the on-linehelp.

[1563] Link—A link is a communications channel or circuit that carries atelecommunications signal between two NEs.

[1564] Logical link—The line displayed on the Topology window thatdepicts one or more physical connections between NEs and/or groups ofNEs is referred to as a logical link. The line only represents theactual network and can be removed without affecting the network. Logicallink names can be edited to conform to the customer's particular namingconvention.

[1565] NE—The term NE refers to hardware only or a combination hardwareand software system that is primarily designed to directly perform atelecommunications service function. For example, an NE is the part ofthe network equipment where a transport entity (such as a line, path, orsection) is terminated and monitored.

[1566] Path—A path at a given rate is a logical connection between thepoints at which a standard frame format for the signal at the given rateis assembled and disassembled.

[1567] Physical link—The line displayed on the Display Link window thatdepicts a physical connection between the ports of two different NEs isreferred to as a physical link. The line only represents the actualnetwork and can be removed without affecting the network. Physical linknames, which are in the format <TID>:<port>::<TID>:<port>, are noteditable.

[1568] Port—In transmission control/Internet protocol (TCP/IP) and userdata protocol (UDP) networks, this is an end point to a logicalconnection. The port number identifies what type of port it is. Forexample, port 80 is used for HTTP traffic.

[1569] Synchronous Transport Signal Level 1 (STS-1)—The STS-1 signal isthe basic logical building block of the SONET signal structure. Itconsists of lower-order signals, payload, and transport overhead for acombined signal rate of 51.84 Mb/s.

[1570] Target identifier (TID)—TIDs uniquely identify NEs. Fujitsu NEsrequire from 7 to 20 alphanumeric characters. NETSMART allows from 1 to20 alphanumeric characters to address non-Fujitsu NEs.

[1571] Time-slot assignment (TSA)—TSA allows STS-1 level traffic to beadded, dropped, or passed through a selected SONET NE. Time slots areassigned on a dedicated basis. Service (i.e., DS1s and/or DS3s) ismapped into these dedicated time slots in the high-speed multiplexedsignal.

[1572] Unidirectional path-switched ring (UPSR)—A UPSR consists of a2-fiber ring. The input signal is bridged in both directions to provideredundant bandwidth. If a fiber is cut or a disruption affects onedirection, the signal is available from the other direction.

[1573] Virtual tributaries (VTs)—VTs are structures designed totransport and switch sub-STS-1 payloads. There are currently four VTsizes: VT1.5 (VT container for a DS1 in SONET), VT2, VT3, and VT6.

[1574] The preferred embodiment described above (Netsmart™) does notdelimit the claimed inventions, but does provide a good indication oftheir advantages, and of the capabilities which can be included in asystem implementing the claimed inventions. Netsmart™ combines featuresof both network management and element management layers of TMN model toprovide comprehensive management capabilities. Netsmart™ can manage verylarge deployments (thousands of network elements, including both Fujitsuand non-Fujitsu elements) while supporting many active users. Netsmart™provides a hierarchical view of the network from large scaleconfiguration down to the shelf and card level, all with a GUI thatdisplays the different scales. Several different views make it easierfor managers to monitor and control what is going on in the system.Netsmart™ also provides graphical control over surveillance,provisioning, software download (SWDL), remote memory backup (RMBU), andremote memory restore (RMR). Netsmart™ also features a rich graphicaluser interface which allows user to perform operational tasks withoutentering data or TL1 Commands.

[1575] Modifications and Variations

[1576] As will be recognized by those skilled in the art, the innovativeconcepts described in the present application can be modified and variedover a tremendous range of applications, and accordingly the scope ofpatented subject matter is not limited by any of the specific exemplaryteachings given.

[1577] Although the presently preferred embodiment has been implementedas an EMS which is designed to interface to an NMS, the disclosedinnovations can be implemented with other choices as to the softwarehierarchy. For example, it is quite possible to combine an NMS with EMSfunctionality, and the dividing line between EMS and NMS is not a sharpdivide. Similarly numerous other functions (such as fault,configuration, account, performance, and/or security management) can becombined if desired with the primary functions of element managementfunctions, and the disclosed inventions can be applied to such expandedarchitectures in various ways.

[1578] The TMN standard describes an overall software architectureconcept which interrelates the various components of telecommunicationssystem management. in addition to element management and neetworkmanagement layers, layers are also reserved for business management andservice management. Other functions can also be combined into thishierarchy. The disclosed innovations are not limited to a system whichis solely an Element Manager System, but can also be applied to othersystems which include element management functionality, even though suchsystems may not be EMS systems strictly speaking.

[1579] None of the description in the present application should be readas implying that any particular element, step, or function is anessential element which must be included in the claim scope: THE SCOPEOF PATENTED SUBJECT MATTER IS DEFINED ONLY BY THE ALLOWED CLAIMS.Moreover, none of these claims are intended to invoke paragraph six of35 USC section 112 unless the exact words “means for” are followed by aparticiple.

What is claimed is:
 1. A computer/software system for managingtelecommunication network elements, comprising: one or moreoperator-driven processes which monitor and manage network elements; andan operator interface which gives operators the option to view groups ofnetwork elements, individual network elements, or subcomponents ofnetwork elements; wherein said operator interface also permits operatorsto optionally command operations on said groups of network elements, oron individual ones of said network elements.
 2. The computer/softwaresystem of claim 1, wherein said operator interface permits operators tooptionally command operations on subcomponents of said network elements.